Hareware-RAID (hptrr) - Slice size changes (FreeBSD 7.0)
HI Guys, I have a new RocketRAID 2320 (http://www.highpoint-tech.com/USA/rr2320.htm) with a 3TB RAID5. But I can not create a 3TB slice. I created the partition in FDISK named da2s1 with a size of 2861178MB (Box AB in ref img attached). I then used the DiskLabel Editor to create a slice with a size of 2794GB (Box C) Looking at the DEV folder I notice two slices have been created da2s1c da2s1d (Box DE) I run 'df -h' to view the size of the D-slice, and it shows as only 723G (box F) I confirm this by re-entering the Label Editor and the slice is now shown as 746GB (Box G), and there is no slice named da2s1c. What could be going wrong here? Kindest regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hareware-RAID (hptrr) - Slice size changes (FreeBSD 7.0)
On Thu, 16 Jul 2009 22:04:16 +1000, ghostcorps ghostco...@gmail.com wrote: Looking at the DEV folder I notice [...] Just for terminology: /dev directory. No folder. FreeBSD doesn't have folders, it has directories. The directory's name is not DEV, it is dev, precise /dev. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Google Earth on FreeBSD 7.0
Hi, I have installed Google Earth via ports but cannot get it to run. If i run it from console, i get this: googleearth ./googleearth-bin: error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file: No such file or directory I have searched for the library it says it cannot find. It is located in /usr/local/lib; /usr/local/lib/libgthread-2.0.so.0 LD_LIBRARY_PATH has that path in its entry. Is there something I am missing. Anybody managed to get it to work? Regards, -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Google Earth on FreeBSD 7.0
On Wed, 1 Jul 2009 12:45:52 +0300, Mike Barnard mike.barna...@gmail.com wrote: LD_LIBRARY_PATH has that path in its entry. Is there something I am missing. If google earth program is a Linux program, have you installed and started the Linux ABI? Maybe the needed library will be required to be located in the /usr/compat/linux/ subtree. Anybody managed to get it to work? Never tried, sorry. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Google Earth on FreeBSD 7.0
On Wed, 1 Jul 2009 12:45:52 +0300, Mike Barnard mike.barna...@gmail.com wrote: LD_LIBRARY_PATH has that path in its entry. Is there something I am missing. If google earth program is a Linux program, have you installed and started the Linux ABI? Maybe the needed library will be required to be located in the /usr/compat/linux/ subtree. Anybody managed to get it to work? Never tried, sorry. Google earth is working on my box. But I am running 7.2 Release. However it is touchy. It will often crash the X server, it's slow and if I change Virtual Desktops during startup It will crash very fast. CRH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: tcllib error while installing tcllib on amd64 system running freebsd 7.0
--- On Mon, 6/8/09, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org
wrote:
From: Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org
Subject: Re: tcllib error while installing tcllib on amd64 system running
freebsd 7.0
To: Dino Vliet dino_vl...@yahoo.com
Cc: freebsd-questions@freebsd.org, m...@freebsd.org, m...@aldan.algebra.com
Date: Monday, June 8, 2009, 10:56 PM
Dino Vliet dino_vl...@yahoo.com writes:
[* ] [8.6b1] comm comm.test!Connect to remote failed: couldn't
open socket: connection timed out
Taking a look in the comm.test file, it looks to me like you already had
something on port 12345, so an attempt to open such a port failed.
--
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
Hi thanks for your answer but I didn't manage to solve this by looking at your
file.
My open ports:
[r...@dual /usr/ports/devel/tcllib]# netstat -na | grep tcp
tcp4 0 0 192.168.2.103.22 192.168.2.100.43051 ESTABLISHED
tcp4 0 0 127.0.0.1.65033 *.* LISTEN
tcp4 0 0 192.168.2.103.22 192.168.2.100.43050 ESTABLISHED
tcp4 0 0 127.0.0.1.25 *.* LISTEN
tcp4 0 0 *.22 *.* LISTEN
tcp6 0 0 *.22 *.* LISTEN
tcp4 0 0 127.0.0.1.5432 *.* LISTEN
tcp6 0 0 ::1.5432 *.* LISTEN
vi work/tcllib-1.11/modules/comm/comm.test
Going to the port line gives me: (I changed it manually to 47557)
test comm-5.0 {-port already in use} {
# First start a server on port 12345
set port 47557
catch {set shdl [socket -server foo $port]}
catch {::comm::comm new bar -port $port -listen 1 -local 0} msg
catch {close $shdl}
unset -nocomplain shdl port
set msg
} {couldn't open socket: address already in use}
The error message I get is:
[* ] [8.6b1] comm comm.test!Connect to remote failed: couldn't open
socket: connection timed out
!while executing
!::comm::comm_cmd_send ::comm::comm 65033 {slaveat 51332}
!(uplevel body line 1)
!invoked from within
!uplevel 1 [linsert $args 0 $method $chan]
!(procedure ::comm::comm line 6)
!invoked from within
!::comm::comm send [lindex $argv 2] [list slaveat [::comm::comm self]]
!(file /usr/ports/devel/tcllib/work/tcllib-1.11/spawn line 9)
Can there be an issue because I have the pf firewall enabled which blocks all?
Brgds
Dino
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: tcllib error while installing tcllib on amd64 system running freebsd 7.0
Dino Vliet dino_vl...@yahoo.com writes: [* ] [8.6b1] comm comm.test!Connect to remote failed: couldn't open socket: connection timed out Taking a look in the comm.test file, it looks to me like you already had something on port 12345, so an attempt to open such a port failed. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
tcllib error while installing tcllib on amd64 system running freebsd 7.0
Hi all,
On my AMD 64 system running freebsd 7.0 I try to install tcllib. I have up to
date ports and have installed tcl86-threaded first.
pkg_info | grep threads gives:
tcl-threads-8.6.b.1_4 Tool Command Language
Installing tcllib gives the following error:
[ * ] [8.6b1] cmdline PASS typed-cmdline-7.30
[ * ] [8.6b1] cmdline typed-cmdline-7.31
[ * ] [8.6b1] cmdline PASS typed-cmdline-7.31
[ * ] [8.6b1] cmdline typed-cmdline-7.32
[ * ] [8.6b1] cmdline PASS typed-cmdline-7.32
[* ] [8.6b1] cmdline typed-cmdline-7.33
[* ] [8.6b1] cmdline PASS typed-cmdline-7.33
[ ] [8.6b1] cmdline ~~ T 137 P 131 S 6 F 0
[* ] [8.6b1]
[* ] [8.6b1] comm
[* ] [8.6b1] comm comm.test!Connect to remote failed: couldn't open
socket: connection timed out
!while executing
!::comm::comm_cmd_send ::comm::comm 62029 {slaveat 54030}
!(uplevel body line 1)
!invoked from within
!uplevel 1 [linsert $args 0 $method $chan]
!(procedure ::comm::comm line 6)
!invoked from within
!::comm::comm send [lindex $argv 2] [list slaveat [::comm::comm self]]
!(file /usr/ports/devel/tcllib/work/tcllib-1.11/spawn line 9)
^Z^C^Z[1] + Suspended make install distclean
# exit
You have stopped jobs.
# exit
What is happening here? I hope someone has a clue.
Brgds
Dino
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0-RELEASE-p12 bind9 log files not found
Hello,
I have setup FreeBSD recently, can somebody help me with one interesting
thing - Bind9 slave DNS server, everything is works great, but I got a
problem with extended logging of xfer, etc.
Bind9 started in chroot:
root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23
/usr/sbin/named -t /var/named -u bind
Configuration of logging channels from named.conf:
logging
{
channel xfer
{
file /var/named/var/log/xfer.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel lame
{
file /var/named/var/log/lame.log versions 2 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel config
{
file /var/named/var/log/conf.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel security
{
file /var/named/var/log/security.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
category xfer-in { xfer; };
category xfer-out { xfer; };
category notify { xfer; };
category lame-servers { lame; };
category config { config; };
category security { security; };
category default { default_syslog; default_debug; };
};
Next, I've create files in /var/named/var/log and chown them to bind:wheel
(cause of -u bind is defined above):
[po...@mgork23-gw /var/named/var/log]$ ls -la
total 4
drwxr-xr-x 2 bind wheel 512 May 30 16:09 .
drwxr-xr-x 6 root wheel 512 May 21 19:16 ..
-rw-r--r-- 1 bind wheel0 May 30 14:54 conf.log
-rw-r--r-- 1 bind wheel0 May 30 14:55 lame.log
-rw-r--r-- 1 bind wheel0 May 30 14:55 security.log
-rw-r--r-- 1 bind wheel0 May 30 14:54 xfer.log
But I get following messages in /var/log/messages:
May 30 16:27:42 srv named[31139]: starting BIND 9.4.2 -t /var/named -u bind
May 30 16:27:42 srv named[31139]: command channel listening on 127.0.0.1#953
May 30 16:27:42 srv named[31139]: command channel listening on ::1#953
May 30 16:27:42 srv named[31139]: logging channel 'xfer' file
'/var/named/var/log/xfer.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'lame' file
'/var/named/var/log/lame.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'config' file
'/var/named/var/log/conf.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'security' file
'/var/named/log/security.log': file not found
May 30 16:27:42 srv named[31139]: running
May 30 16:27:42 srv named[31139]: isc_log_open '/var/named/var/log/xfer.log'
failed: file not found
Changing permissions and putting log-files in different places (with
changing paths in named.conf of course) has no effect. I see that problem is
pretty silly but searching info about this doesn't say something special - I
still got file not found in /var/messages.
Maybe Iam don't understand where files must be placed, so, thanks in advance
for everybody who can explain how it works :)
VP
v.prokof...@gmail.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 14:50:31 Prokofyev Vladislav wrote:
Bind9 started in chroot:
root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23
/usr/sbin/named -t /var/named -u bind
Configuration of logging channels from named.conf:
logging
{
channel xfer
{
file /var/named/var/log/xfer.log versions 3 size
10m;
The named running chrooted has no clue about /var/named. You can either use
ducttape:
cd /var/named/var sudo ln -s .. named
or just strip /var/named from your config file, hence use /var/log/xfer.log.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
Prokofyev Vladislav wrote: Hello, I have setup FreeBSD recently, can somebody help me with one interesting thing - Bind9 slave DNS server, everything is works great, but I got a problem with extended logging of xfer, etc. Bind9 started in chroot: root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23 /usr/sbin/named -t /var/named -u bind [snip] Changing permissions and putting log-files in different places (with changing paths in named.conf of course) has no effect. I see that problem is pretty silly but searching info about this doesn't say something special - I still got file not found in /var/messages. Maybe Iam don't understand where files must be placed, so, thanks in advance for everybody who can explain how it works :) Don't know if this will help, but took a quick look at my box here at home and have the following in my rc.conf - but I don't have logging turned on with this machine. Note the last line. So the logs should be in /var/named/var/log named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike After adding these options on my system, named didn't start at boot. Manully attempt to start it via '/etc/rc.d/named start' brought to the following error: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named Anyway, thank you for time you've spent to write an answer. Hope this thread will help somebody who is stuck with the same problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 17:01:17 Prokofyev Vladislav wrote: The named running chrooted has no clue about /var/named. You can either use ducttape: cd /var/named/var sudo ln -s .. named or just strip /var/named from your config file, hence use /var/log/xfer.log. -- Mel This helped, thank you a lot. So, if I think in a right way, /usr/sbin/named with -t start option don't effect on any symlinks etc. Erm, yes or ... no. I suggest you read up on chroot. The short answer is that relative symlinks within the chroot environment work while absolute ones should take into the account the new filesystem root. I didn't pay attention to this cause named(8) says: -t directory Chroot to directory after processing the command line arguments, but before reading the configuration file. and have a look at what /etc/namedb really is: # ls -l /etc/namedb lrwxr-xr-x 1 root wheel 21 May 21 06:24 /etc/namedb - /var/named/etc/namedb And this demonstrates chroot a bit: # cp /rescue/ls /var/named/ # chroot /var/named /ls -l /etc/namedb total 1 drwxr-xr-x 2 53 0512 Feb 28 05:57 dynamic drwxr-xr-x 2 0 0512 May 15 13:42 master -rw-r--r-- 1 0 0 11714 May 15 14:40 named.conf -rw-r--r-- 1 0 0 2956 May 15 13:42 named.root -rw--- 1 53 0 97 Apr 18 10:29 rndc.key drwxr-xr-x 2 53 0512 May 30 11:21 slave Warning: This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance security on most systems; the way chroot(2) is defined allows a process with root privileges to escape a chroot jail. And I thought that all actions for proper work are made by named :) They are, you just need reference the right path, the one without /var/named, or use relative paths where the working directory is /etc/namedb. So one would get to /var/log using: file ../../var/log/xfer; -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0 Boot Failure
Hello, When I boot a Dell Optiplex 320 running FreeBSD 7.0 the boot sequence hangs at USB3: OHCI version 1.0, legacy support if a keyboard is plugged in. It will boot successfully if the keyboard is not plugged in until after the boot sequence is completed. Normally this would not be that big of deal for most people, but I have 120 of these Dell machines running FreeBSD 7.0 and unplugging keyboards before the boot sequence starts is rather problematic. Thank you, Matt Hewitt President Pacific Crest Research 801-866-1116 x111 801-866-0280 Fax Always ask for exactly what you want, you just might get it! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[NS]freebsd 7.0 could not send Neighbor Solicitation when I reboot the freebsd
Hello, everyone: when I reboot freebsd7.0, it did not send NS package, I only can receive RS. could you tell me why. tcpdump log info: reading from file 1.2.A, link-type EN10MB (Ethernet) 13:20:11.994102 IP6 fe80::2e0:4cff:fe19:129f ff02::2: ICMP6, router solicitation, length 16 13:20:11.994107 IP6 fe80::2e0:4cff:fe19:129f ff02::2: ICMP6, router solicitation, length 16 13:20:14.546713 IP6 fe80::2e0:4cff:fe19:129f ff02::2:fc25:dbcf: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::2:fc25:dbcf, length 24 13:20:14.546725 IP6 fe80::2e0:4cff:fe19:129f ff02::2:fc25:dbcf: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::2:fc25:dbcf, length 24 13:20:15.546584 IP6 fe80::2e0:4cff:fe19:129f ff02::1:ff19:129f: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ff19:129f, length 24 13:20:15.546595 IP6 fe80::2e0:4cff:fe19:129f ff02::1:ff19:129f: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ff19:129f, length 24 13:20:15.993560 IP6 fe80::2e0:4cff:fe19:129f ff02::2: ICMP6, router solicitation, length 16 13:20:15.993567 IP6 fe80::2e0:4cff:fe19:129f ff02::2: ICMP6, router solicitation, length 16 13:20:19.994014 IP6 fe80::2e0:4cff:fe19:129f ff02::2: ICMP6, router solicitation, length 16 13:20:19.994021 IP6 fe80::2e0:4cff:fe19:129f ff02::2: ICMP6, router solicitation, length 16 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
nomachine on Freebsd 7.0-release 64-bit in a jail
It appears that the both the FreeNX port and the binary nomachine nxserver ports are both broken and fail to compile. I'm still trying to get nxserver 3 free forever edition to work. So far I've made some mods to it's install scripts but I'm bumping up against a strange licensing error (there is no license for the free edition). Before I bang my head on this much longer, has anyone else gotten Nomachine's version 3 server working on FreeBSD 7? How about in a jail? How does one mount linprocfs in a jail? Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Well it is possible - but what information it can give me? Could you explain - just to know if this 2 hours is acceptable for this. Check DELL website for more info - but generally tests the harwrare componnents.. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Wednesday 28 January 2009 11:24:50 Kirk Strauser wrote: On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. Right, you really want to do buildworld on a production machine that experiences random reboots. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Jan 28, 2009, at 3:45 PM, Mel wrote: On Wednesday 28 January 2009 11:24:50 Kirk Strauser wrote: On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. Right, you really want to do buildworld on a production machine that experiences random reboots. That would make the situation worse how? The worst case is that it fails during installkernel, leaving him to boot from kernel.old. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Wednesday 28 January 2009 13:24:59 Kirk Strauser wrote: On Jan 28, 2009, at 3:45 PM, Mel wrote: On Wednesday 28 January 2009 11:24:50 Kirk Strauser wrote: On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. Right, you really want to do buildworld on a production machine that experiences random reboots. That would make the situation worse how? The worst case is that it fails during installkernel, leaving him to boot from kernel.old. The worst case is 1 to N random reboots during buildworld (been there, done that), leaving the filesystem inconsistent, needing an fsck -y, unless you trust background_fsck, then finding out it's the hardware, not the OS. It's easy to find out if the OS panics, by enabling crash dumps. Then you can still decide whether an upgrade might fix it and you may even get a clue as to which hardware or kernel subsystem is affected, if the kernel dumps. I've had a machine where I never got buildworld to finish, tried 4 or 5 times hoping to get lucky this time... Reapplying thermal paste to the CPU heatsink made everything work. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0 reboots on Dell 2950
Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
- Original Message From: Proskurin Kirill proskurin...@fxclub.org To: freebsd-questions freebsd-questions@freebsd.org Sent: Tuesday, January 27, 2009 12:07:25 PM Subject: FreeBSD 7.0 reboots on Dell 2950 Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? -- Best regards, Proskurin Kirill I think you should upgrade to FreeBSD 7.1-RELEASE at least, if not -STABLE. Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Abdullah Ibn Hamad Al-Marri wrote: - Original Message From: Proskurin Kirill proskurin...@fxclub.org To: freebsd-questions freebsd-questions@freebsd.org Sent: Tuesday, January 27, 2009 12:07:25 PM Subject: FreeBSD 7.0 reboots on Dell 2950 Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? I think you should upgrade to FreeBSD 7.1-RELEASE at least, if not -STABLE. Well - why I must do this? It is was a some problems with 7.0? I don`t want to do this just to do this. Well - if nothing helps may be. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Check the fan on the CPU. Probably it's dead or malfunctioning. Also check the heat sink underneath the fan. It could be dirty and blocking the airflow. Regards, Mikhail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
- Original Message From: Proskurin Kirill proskurin...@fxclub.org To: Abdullah Ibn Hamad Al-Marri wearab...@yahoo.ca; FreeBSD Questions Mailing List freebsd-questions@freebsd.org Sent: Tuesday, January 27, 2009 12:45:46 PM Subject: Re: FreeBSD 7.0 reboots on Dell 2950 Abdullah Ibn Hamad Al-Marri wrote: - Original Message From: Proskurin Kirill To: freebsd-questions Sent: Tuesday, January 27, 2009 12:07:25 PM Subject: FreeBSD 7.0 reboots on Dell 2950 Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? I think you should upgrade to FreeBSD 7.1-RELEASE at least, if not -STABLE. Well - why I must do this? It is was a some problems with 7.0? I don`t want to do this just to do this. Well - if nothing helps may be. -- Best regards, Proskurin Kirill Because there are many bugs were in 7.0 and got fixed in 7.1, and maybe you are affected by one of them. Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Mikhail Goriachev wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) Check the fan on the CPU. Probably it's dead or malfunctioning. Also check the heat sink underneath the fan. It could be dirty and blocking the airflow. No - fan is work good. It is not a heat problem. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Peter Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Peter wrote: Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Do you think it can be a problem? It is possible to test it some how? This host is really far away from me. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? I know it works w/ the Dell controllers, I have also had issues with it where it randomly made my machines (all Power Edge 2950 running 7.x) core dump ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Michael Toth wrote: Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? I know it works w/ the Dell controllers, I have also had issues with it where it randomly made my machines (all Power Edge 2950 running 7.x) core dump mail# cd /usr/ports/sysutils/megarc mail# make install clean === megarc-1.51 is marked as broken: Running megarc seems to cause memory corruption. *** Error code 1 Stop in /usr/ports/sysutils/megarc. mail# Hm. Do I really need it? :-) -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Tuesday 27 January 2009 01:02:00 Abdullah Ibn Hamad Al-Marri wrote: Because there are many bugs were in 7.0 and got fixed in 7.1, and maybe you are affected by one of them. Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. At the very least, we should find out if the OS is at fault at all. For Proskurin: Find out if the machine reboots, because of a kernel panic and if so try to get a kernel crash dump [1]. If it does not panic, you're 90% sure it's a hardware issue. The remaining 10% is left for the case where FreeBSD does not configure hardware correctly through ACPI, causing hardware to operate badly. [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Peter wrote: Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Do you think it can be a problem? It is possible to test it some how? This host is really far away from me. Last 3 months I had issues will DELL 1650 and DELL R200. In both cases BIOS update fixed it. 1) DELL 1650 - FreeBSD did not want to installl, after BIOS udpate all went well 2) DELL R200 with SATA - no problems 2) DELL R200 with SAS, installed well, extremely scary message about HDD, after BIOS update, RAID controller BIOS udpate and RAID controller firmware udpate all went well BTW when the R200 scared me , I got a DELL diagniostic CD with FreeDOS and it did full system test. If you can get KVM over IP, have someone to put in the CD and 2 hours downtime is acceptable, it is good idea to run that CD on your machine. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Peter пишет: Proskurin Kirill wrote: Peter wrote: Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Do you think it can be a problem? It is possible to test it some how? This host is really far away from me. Last 3 months I had issues will DELL 1650 and DELL R200. In both cases BIOS update fixed it. 1) DELL 1650 - FreeBSD did not want to installl, after BIOS udpate all went well 2) DELL R200 with SATA - no problems 2) DELL R200 with SAS, installed well, extremely scary message about HDD, after BIOS update, RAID controller BIOS udpate and RAID controller firmware udpate all went well BTW when the R200 scared me , I got a DELL diagniostic CD with FreeDOS and it did full system test. If you can get KVM over IP, have someone to put in the CD and 2 hours downtime is acceptable, it is good idea to run that CD on your machine. Well it is possible - but what information it can give me? Could you explain - just to know if this 2 hours is acceptable for this. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? I know it works w/ the Dell controllers, I have also had issues with it where it randomly made my machines (all Power Edge 2950 running 7.x) core dump mail# cd /usr/ports/sysutils/megarc mail# make install clean === megarc-1.51 is marked as broken: Running megarc seems to cause memory corruption. *** Error code 1 Stop in /usr/ports/sysutils/megarc. mail# Hm. Do I really need it? :-) No, you do not really need it, it would just allow you to get information from the raid controller (and as I said before this port caused me issues and core dump'd my machines) I was more trying to get at IF you were running this that if may have been the cause of your issues. As someone else has already mentioned you really need to find out if there is a kernel panic or not and going from there. -- -- [ Queldor ] (Warning: This message may cause you to understand something) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
mail# cd /usr/ports/sysutils/megarc mail# make install clean === megarc-1.51 is marked as broken: Running megarc seems to cause memory corruption. We have a PR open on that - ports/130326: http://groups.google.com/group/lucky.freebsd.ports.bugs/browse_thread/thread/14c7c3b8261e8be7/f8cd79bbd9404609?lnk=raotpli=1 ~BAS *** Error code 1 Stop in /usr/ports/sysutils/megarc. mail# Hm. Do I really need it? :-) IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Closure: Vetting motherboard Gigabyte GA-MA78G-DS3H for FreeBSD 7.0-RELEASE
Frank Shute-2 wrote: I've had good luck with anything by Asus and Gigabyte. I tend to avoid boards with bleeding edge hardware/features as these will not have received so much testing (and may not even be supported) on FreeBSD. This in practice means get a board that's been on sale for a bit. In my research and unwitting trials with this particular motherboard (Gigabyte GA-MA78G-DS3H), I found that, while it is generally well tolerated by FreeBSD 7.1-RELEASE, the onboard RAID is completely incompatible. Even when a RocketRAID 3120 card was used, the RAID could be built, but the ar0 device thus created, did not survive a reboot. Also, a software RAID was attempted -- after a minimal install from CD, the atacontrol command was used to create RAID ar0, then (without rebooting) exiting back to the installer, the OS was loaded onto it; however, upon reboot, ar0 could not be found. In other words, it could not boot from any RAID, whether by software in FreeBSD or by hardware on RocketRAID. The problem stems from the board's Southbridge SB700 chipset (the infamous 700 series). This chipset is not (yet?) supported in FreeBSD. Other notes on this board include the following: -Generic VGA worked. -The onboard LAN (chipset 8111C) worked in 7.1-RELEASE, but not 7.0. -If the SATA ports are put into AHCI or Native IDE modes, individual disks were recognized, but in RAID mode, neither the RAID nor individual disks could be seen. -- View this message in context: http://www.nabble.com/Re%3A-Vetting-motherboard-Gigabyte-GA-MA78G-DS3H-for-FreeBSD-7.0-RELEASE-tp21100783p21591458.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0 Installation error
Hi people, Hi people, I am Tom and I have been attempting to install FreeBSD 7.0 from a dvd. I put the dvd in the drive and boot, the boot screen appears with the options default, acpi disabled, safe mode, etc, I then select default. The hardware probing/detecting scrolls by and then comes to a halt with the following line: GEOM_LABLE: Lable for provider acd0 is is09660/FreeBSD 7. I have also on other boot attempts tried acpi disabled, safe mode with the same outcome. Have selected single user on another attempt and sysinstall program boots, after going through setting up the hard drive and paritions durring the install of the os the following error occurs numerous times: Write failure on transfer! (write 0 bytes of 1425408 bytes) 100% Just wondering if this has occured to any one else and how they got around it. Look forward to replys, thanks Tom Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 Installation error
This is a listing of my hardware, I probably should have listed it in my earlier post. Hardware: Motherboard: A7N8X-E Deluxe socket A (462) Chipset: Northbridge: NVIDIA nforce2 spp ultra400 Southbrdige nvidia nforce2 MCP-T memory ddr 184pin (maximum of 3x184) I have kingston kvr400x64c3ak 512mb pc3200 (two pieces) ram installed.. on board audio: mcp-t southbridge + realtec alc50 6channel audio codec networking: Marvell 88e8001 gigibit, mcp-t southbridge controller mac + realtec 8201BL phy 1394: mcp-t southbridge ieee 1394a controller + realtec 8801BL phy internal connectors: usb2 connectors, games/midi, 2 ide, 20pin atx power, 2 sata, 2 1394, 5 pci, 1 asus propriety wi-fi slot and a couple others. Hard drive is a Western Digital WD2000jb ide caviar 200GB optical drive: asus drw-1604p (jumper cap is on cable select at the moment. However there are five rows of pins, three are cable select, master and secondary, no idea what the other two are) Graphics card is an asus A9600 series AGP ati From what I remember seeing fly by on the screen last night the majority of the motherboard parts were detected including the rear panel connectors which I did not list (if you want me to list those, let me know). Hope this helps. Thanks Tom --- On Tue, 13/1/09, T D ttd...@yahoo.com.au wrote: From: T D ttd...@yahoo.com.au Subject: FreeBSD 7.0 Installation error To: freebsd-questions@freebsd.org Received: Tuesday, 13 January, 2009, 11:04 PM Hi people, Hi people, I am Tom and I have been attempting to install FreeBSD 7.0 from a dvd. I put the dvd in the drive and boot, the boot screen appears with the options default, acpi disabled, safe mode, etc, I then select default. The hardware probing/detecting scrolls by and then comes to a halt with the following line: GEOM_LABLE: Lable for provider acd0 is is09660/FreeBSD 7. I have also on other boot attempts tried acpi disabled, safe mode with the same outcome. Have selected single user on another attempt and sysinstall program boots, after going through setting up the hard drive and paritions durring the install of the os the following error occurs numerous times: Write failure on transfer! (write 0 bytes of 1425408 bytes) 100% Just wondering if this has occured to any one else and how they got around it. Look forward to replys, thanks Tom Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 Installation error
Hopefully I am posting to the correct list...Or should I be posting to freebsd-stable? --- On Wed, 14/1/09, T D ttd...@yahoo.com.au wrote: From: T D ttd...@yahoo.com.au Subject: Re: FreeBSD 7.0 Installation error To: freebsd-questions@freebsd.org Received: Wednesday, 14 January, 2009, 6:58 AM This is a listing of my hardware, I probably should have listed it in my earlier post. Hardware: Motherboard: A7N8X-E Deluxe socket A (462) Chipset: Northbridge: NVIDIA nforce2 spp ultra400 Southbrdige nvidia nforce2 MCP-T memory ddr 184pin (maximum of 3x184) I have kingston kvr400x64c3ak 512mb pc3200 (two pieces) ram installed... on board audio: mcp-t southbridge + realtec alc50 6channel audio codec networking: Marvell 88e8001 gigibit, mcp-t southbridge controller mac + realtec 8201BL phy 1394: mcp-t southbridge ieee 1394a controller + realtec 8801BL phy internal connectors: usb2 connectors, games/midi, 2 ide, 20pin atx power, 2 sata, 2 1394, 5 pci, 1 asus propriety wi-fi slot and a couple others. Hard drive is a Western Digital WD2000jb ide caviar 200GB optical drive: asus drw-1604p (jumper cap is on cable select at the moment. However there are five rows of pins, three are cable select, master and secondary, no idea what the other two are) Graphics card is an asus A9600 series AGP ati From what I remember seeing fly by on the screen last night the majority of the motherboard parts were detected including the rear panel connectors which I did not list (if you want me to list those, let me know). Hope this helps. Thanks Tom --- On Tue, 13/1/09, T D ttd...@yahoo.com.au wrote: From: T D ttd...@yahoo.com.au Subject: FreeBSD 7.0 Installation error To: freebsd-questions@freebsd.org Received: Tuesday, 13 January, 2009, 11:04 PM Hi people, Hi people, I am Tom and I have been attempting to install FreeBSD 7.0 from a dvd. I put the dvd in the drive and boot, the boot screen appears with the options default, acpi disabled, safe mode, etc, I then select default. The hardware probing/detecting scrolls by and then comes to a halt with the following line: GEOM_LABLE: Lable for provider acd0 is is09660/FreeBSD 7. I have also on other boot attempts tried acpi disabled, safe mode with the same outcome. Have selected single user on another attempt and sysinstall program boots, after going through setting up the hard drive and paritions durring the install of the os the following error occurs numerous times: Write failure on transfer! (write 0 bytes of 1425408 bytes) 100% Just wondering if this has occured to any one else and how they got around it. Look forward to replys, thanks Tom Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
On Fri, Jan 09, 2009 at 08:46:54PM -0500, Garance A Drosihn wrote: At 2:09 PM -0800 1/4/09, David Christensen wrote: I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? Why do that? Just create your own root account, put what you want for a shell on that account and use it. Use vipw. Copy the root line and then change the _second_ one to be your own root id- say, Rgad - and make a loging in directory for it. Change the directory part of the pw entry to be that and the the shell to be what you want. Then change the password to be what you want or use some pwvault utility or whatever. Just make sure you specify the second root account (Rgad) when doing so or it will change the real root's password. jerry What I do is add the following lines to /root/.login : if ($?prompt) then if ( -x /usr/local/bin/bash ) then # echo Switching to bash setenv SHELL /usr/local/bin/bash exec /usr/local/bin/bash -login endif endif I've been doing this for at least 10 years. I haven't had any problems with it, but Your Mileage Might Vary. -- Garance Alistair Drosehn= g...@gilead.netel.rpi.edu Senior Systems Programmer or g...@freebsd.org Rensselaer Polytechnic Instituteor dro...@rpi.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
David Christensen dpchr...@holgerdanske.com writes: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? Assuming you build the shell statically linked, and put it in the root partition, you're unlikely to have any trouble. However: - that is what the toor user is for - in my own opinion, anyone who cares what shell root runs is probably spending too much time running as root -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
At 2:09 PM -0800 1/4/09, David Christensen wrote: I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? What I do is add the following lines to /root/.login : if ($?prompt) then if ( -x /usr/local/bin/bash ) then # echo Switching to bash setenv SHELL /usr/local/bin/bash exec /usr/local/bin/bash -login endif endif I've been doing this for at least 10 years. I haven't had any problems with it, but Your Mileage Might Vary. -- Garance Alistair Drosehn= g...@gilead.netel.rpi.edu Senior Systems Programmer or g...@freebsd.org Rensselaer Polytechnic Instituteor dro...@rpi.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0-Stable Crashed with Cacti
Dear All, we face problem with running cacti on FreeBSD 7.0-Stable. From top command output: last pid: 5836; load averages: 0.03, 0.17, 0.24 up 0+01:17:30 15:24:11 96 processes: 1 running, 95 sleeping CPU: 0.2% user, 0.0% nice, 1.5% system, 0.0% interrupt, 98.3% idle Mem: 736M Active, 125M Inact, 127M Wired, 300K Cache, 111M Buf, 3776K Free Swap: 2014M Total, 2014M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 1054 root1 760 118M 94916K pfault 1 0:07 0.00% php 1382 root1 760 110M 87224K pfault 1 0:07 0.00% php 1740 root1 760 103M 75576K pfault 0 0:06 0.00% php 2120 root1 760 97160K 74056K pfault 1 0:06 0.00% php 2451 root1 760 91016K 79316K pfault 1 0:05 0.00% php 2818 root1 760 83848K 72324K pfault 1 0:05 0.00% php 3147 root1 760 76680K 64856K pfault 1 0:04 0.00% php 3511 root1 760 69512K 57836K pfault 1 0:04 0.00% php 3823 root1 760 62344K 50880K pfault 1 0:03 0.00% php 4170 root1 760 55176K 43568K pfault 0 0:03 0.00% php 4513 root1 760 48008K 36480K pfault 1 0:02 0.00% php 4847 root1 760 40840K 29452K pfault 1 0:02 0.00% php 5180 root1 760 33672K 22664K pfault 0 0:01 0.00% php 5810 root1 -8 19 11696K 9344K piperd 1 0:01 0.00% perl 5534 root1 760 26504K 15612K pfault 0 0:01 0.00% php 5811 root1 -8 19 11876K 9488K piperd 1 0:01 0.00% perl 5812 root1 -8 19 11676K 9304K piperd 1 0:01 0.00% perl 1651 root1 440 8400K 2440K select 1 0:01 0.00% sshd 839 root1 440 21536K 9152K select 0 0:00 0.00% httpd 747 root1 440 7372K 4996K select 0 0:00 0.00% perl 658 root1 440 8808K 4096K select 1 0:00 0.00% snmpd 5814 root1 760 10588K 4016K pfault 1 0:00 0.00% php 1655 root1 80 4404K 1600K wait 1 0:00 0.00% bash 746 mysql 24 40 70884K 21936K sbwait 1 0:00 0.00% mysqld 858 root1 440 5864K 2152K select 1 0:00 0.00% sendmail 5835 root1 440 3504K 1520K CPU0 0 0:00 0.00% top 652 root1 440 7824K 3048K select 1 0:00 0.00% snmptrapd 5809 root1 80 3472K 1008K wait 0 0:00 0.00% sh 5808 root1 80 3472K 1008K wait 1 0:00 0.00% sh 870 root1 -160 3200K 1072K vmwait 0 0:00 0.00% cron 5827 root1 76 19 3204K 1480K pfault 0 0:00 0.00% rateup 5828 root1 76 19 3204K 1472K pfault 0 0:00 0.00% rateup 5819 root1 -80 3200K 1108K piperd 0 0:00 0.00% cron 5820 root1 80 3472K 1004K wait 0 0:00 0.00% sh 577 root1 440 3172K 1008K select 1 0:00 0.00% syslogd 5823 root1 760 10588K 4112K pfault 1 0:00 0.00% php 5829 root1 76 19 3204K 1332K pfault 1 0:00 0.00% rateup We realized that all cacti process just eat my cpu and memory (STATE: pfault) and my server should be reboot. Is there any way how to fix it? Thank you Kalpin Erlangga Silaen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0-Stable Crashed by Cacti
Dear all, we faced problem with running cacti on FreeBSD 7.0-Stable. From top command output: last pid: 5836; load averages: 0.03, 0.17, 0.24 up 0+01:17:30 15:24:11 96 processes: 1 running, 95 sleeping CPU: 0.2% user, 0.0% nice, 1.5% system, 0.0% interrupt, 98.3% idle Mem: 736M Active, 125M Inact, 127M Wired, 300K Cache, 111M Buf, 3776K Free Swap: 2014M Total, 2014M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 1054 root1 760 118M 94916K pfault 1 0:07 0.00% php 1382 root1 760 110M 87224K pfault 1 0:07 0.00% php 1740 root1 760 103M 75576K pfault 0 0:06 0.00% php 2120 root1 760 97160K 74056K pfault 1 0:06 0.00% php 2451 root1 760 91016K 79316K pfault 1 0:05 0.00% php 2818 root1 760 83848K 72324K pfault 1 0:05 0.00% php 3147 root1 760 76680K 64856K pfault 1 0:04 0.00% php 3511 root1 760 69512K 57836K pfault 1 0:04 0.00% php 3823 root1 760 62344K 50880K pfault 1 0:03 0.00% php 4170 root1 760 55176K 43568K pfault 0 0:03 0.00% php 4513 root1 760 48008K 36480K pfault 1 0:02 0.00% php 4847 root1 760 40840K 29452K pfault 1 0:02 0.00% php 5180 root1 760 33672K 22664K pfault 0 0:01 0.00% php 5810 root1 -8 19 11696K 9344K piperd 1 0:01 0.00% perl 5534 root1 760 26504K 15612K pfault 0 0:01 0.00% php 5811 root1 -8 19 11876K 9488K piperd 1 0:01 0.00% perl 5812 root1 -8 19 11676K 9304K piperd 1 0:01 0.00% perl 1651 root1 440 8400K 2440K select 1 0:01 0.00% sshd 839 root1 440 21536K 9152K select 0 0:00 0.00% httpd 747 root1 440 7372K 4996K select 0 0:00 0.00% perl 658 root1 440 8808K 4096K select 1 0:00 0.00% snmpd 5814 root1 760 10588K 4016K pfault 1 0:00 0.00% php 1655 root1 80 4404K 1600K wait 1 0:00 0.00% bash 746 mysql 24 40 70884K 21936K sbwait 1 0:00 0.00% mysqld 858 root1 440 5864K 2152K select 1 0:00 0.00% sendmail 5835 root1 440 3504K 1520K CPU0 0 0:00 0.00% top 652 root1 440 7824K 3048K select 1 0:00 0.00% snmptrapd 5809 root1 80 3472K 1008K wait 0 0:00 0.00% sh 5808 root1 80 3472K 1008K wait 1 0:00 0.00% sh 870 root1 -160 3200K 1072K vmwait 0 0:00 0.00% cron 5827 root1 76 19 3204K 1480K pfault 0 0:00 0.00% rateup 5828 root1 76 19 3204K 1472K pfault 0 0:00 0.00% rateup 5819 root1 -80 3200K 1108K piperd 0 0:00 0.00% cron 5820 root1 80 3472K 1004K wait 0 0:00 0.00% sh 577 root1 440 3172K 1008K select 1 0:00 0.00% syslogd 5823 root1 760 10588K 4112K pfault 1 0:00 0.00% php 5829 root1 76 19 3204K 1332K pfault 1 0:00 0.00% rateup all cacti process just eat my memory and cpu, after that my server crashed and should be reboot. How to fix this problem? Thank you Kalpin Erlangga Silaen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-Stable Crashed with Cacti
On Tue, Jan 6, 2009 at 3:30 AM, Kalpin Erlangga Silaen kal...@muliahost.com wrote: Dear All, we face problem with running cacti on FreeBSD 7.0-Stable. From top command output: - snip - We realized that all cacti process just eat my cpu and memory (STATE: pfault) and my server should be reboot. Is there any way how to fix it? Thank you Kalpin Erlangga Silaen Cacti runs the poller script using php. It looks like the poller script is taking too long to finish, and it ends up having several instances running at the same time. I'd recommend that you look into the 'Spine' poller (formally known as Cactid). It's a threading C program, which is _MUCH_ faster than php will ever be. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-Stable Crashed with Cacti
On Tue, Jan 6, 2009 at 3:30 AM, Kalpin Erlangga Silaen kal...@muliahost.com wrote: Dear All, we face problem with running cacti on FreeBSD 7.0-Stable. From top command output: - snip - We realized that all cacti process just eat my cpu and memory (STATE: pfault) and my server should be reboot. Is there any way how to fix it? Thank you Kalpin Erlangga Silaen Cacti runs the poller script using php. It looks like the poller script is taking too long to finish, and it ends up having several instances running at the same time. I'd recommend that you look into the 'Spine' poller (formally known as Cactid). It's a threading C program, which is _MUCH_ faster than php will ever be. ___ Thank you for reply. I've change to spine poller. I'll try to update if we face same problem. thank's Kalpin Erlangga Silaen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
On Sun, Jan 04, 2009 at 02:09:03PM -0800, David Christensen wrote: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? I change my root shell to pdksh. It's statically linked and I copy it from /usr/local/bin to /bin. In single user mode you're prompted for a shell (/bin/sh is the default) so I usually use that. I've never had any problems (famous last words ;) Just have to remember to copy the executable to the root filesystem if your shell gets upgraded. What you don't want to do is overwrite /bin/sh with /bin/bash or anything like that. The boot up scripts depend on /bin/sh and although bash is meant to be Bourne compatible, I wouldn't trust it myself to bring up the system without problems. TIA, David Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? TIA, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
Does anybody know if it's okay to change the root shell? A topic of debate, but yes it is okay to change the root shell, but there are some things to know... Some people fret about the idea that shells like bash are not on the root partition and are usually dynamically linked to libraries which reside on /usr and are therefore not available in single-user mode. (One could install a static version of bash to avoid this.) Additionally, FreeBSD prompts the user for the path to the desired shell when going into single-user mode. Shells like sh and tcsh, while dynamically linked, their libs reside on the root partition. If that isn't enough, statically linked shells exist in /rescue and therefore should always be available. Furthermore, the installation CD can be booted from and can provide an emergency repair shell. So yes, there is no technical reason you cannot change the root shell. Just be aware that a default bash install will not be available in single-user mode. But... best security practices dictate that you should not be using the root shell. If you're using the root shell often enough to find the default shell inconvenient, you should consider using something like sudo and a regular user account instead. You can use the builtin 'su' command with the '-m' flag to preserve the environment of the current user, while elevating your privileges. The shell used will be the login shell of the user issuing the 'su' command. Only members of the group 'wheel' may issue the 'su' command. -Modulok- On 1/4/09, David Christensen dpchr...@holgerdanske.com wrote: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? TIA, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
On Sun, Jan 4, 2009 at 5:09 PM, David Christensen dpchr...@holgerdanske.com wrote: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-serverhttp://portsmon.freebsd.org/portoverview.py?category=miscportname=amanda-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? TIA, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org well you will lock yourself out of the system if you uninstall bash or bash breaks. I would enable toor just in case ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
From: SDH Admin ad...@stardothosting.com How can I do this if the systeem freezes??? Good old fashioned pen + paper (as long as it's not too long). Never fails. Main problem is: ad0: FreeBSD check1 failed I googled but didn't find any solution. Does anyone have a clue where to find the solution? Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
Jack Raats j...@jarasoft.net writes: From: SDH Admin ad...@stardothosting.com How can I do this if the systeem freezes??? Good old fashioned pen + paper (as long as it's not too long). Never fails. Main problem is: ad0: FreeBSD check1 failed I googled but didn't find any solution. Does anyone have a clue where to find the solution? According to my quick look at the code, that message isn't necessarily a hint to the problem. Do you have a RAID array in the machine? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
On 2008-Dec-24 17:29:05 +0100, Jack Raats j...@jarasoft.net wrote: Main problem is: ad0: FreeBSD check1 failed This is produced when the ATA subsystem is trying to read RAID metadata off the disk and just means it failed to find any. It's not an error. Can you post more context please. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpTdruFiT2UV.pgp Description: PGP signature
Re: Problems installing FreeBSD 7.0
On 2008-Dec-23 20:32:38 +0100, Jack Raats j...@jarasoft.net wrote: Can you try to paste exactly what was on the screen before the freeze for both 6.4 and 7.0? How can I do this if the systeem freezes??? Take a photo and put it up somewhere (http://imagebin.ca/ if nowhere else). If scroll lock still works, you can take pictures of earlier output (and if caps/scroll/num lock don't work, that is a useful piece of information). -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgp7MuaXmUzVi.pgp Description: PGP signature
Problems installing FreeBSD 7.0
Hi, At this moment I have problems installing FreeBSD 6.4 and FreeBSD 7.0. After booting from CD the system I get the menu. I have tried all possible options. The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can anyone help me. I never had this problems before on other systems. Thanks Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
On Tue, Dec 23, 2008 at 1:30 PM, Jack Raats j...@jarasoft.net wrote: Hi, At this moment I have problems installing FreeBSD 6.4 and FreeBSD 7.0. After booting from CD the system I get the menu. I have tried all possible options. The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can anyone help me. I never had this problems before on other systems. Have you tried disabling DMA or ACPI? hw.ata.ata_dma=0 -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
- Original Message - From: SDH Admin ad...@stardothosting.com The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can you try to paste exactly what was on the screen before the freeze for both 6.4 and 7.0? How can I do this if the systeem freezes??? Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Problems installing FreeBSD 7.0
The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can you try to paste exactly what was on the screen before the freeze for both 6.4 and 7.0? Thanks. --- Kevin K. Systems Administrator www.stardothosting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Problems installing FreeBSD 7.0
How can I do this if the systeem freezes??? Good old fashioned pen + paper (as long as it's not too long). Never fails. --- Kevin K. Systems Administrator www.stardothosting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Vetting motherboard Gigabyte GA-MA78G-DS3H for FreeBSD 7.0-RELEASE
On Thu, Dec 18, 2008 at 09:15:33AM -0800, ThinkDifferently wrote: I'm currently looking for an ATX motherboard that supports the AM2+ socket, Phenom Quad-Core processor, 4 DDR2 RAM slots (800 MHz is fine), 6 SATA ports with RAID, and Gigabit LAN. Onboard VGA would be nice. It needs to work well with FreeBSD 7.0-RELEASE, using a 2-disk SATA RAID1. I'm currently looking at the Gigabyte GA-MA78G-DS3H. Has anyone successfully operated 7.0 on this board? Any booting issues? Did you need to modify the ISO to get it to boot (if so how)? Did RAID work? Did it require a special driver to be loaded (if so how)? Do any other motherboards fit the bill, given the specifications I give above? I recently got a black eye -( with the MSI K9N2G Neo-FD, using the GeForce 8200 (MCP78) chipset. FreeBSD 7.0-RELEASE and CentOS 5.2 wouldn't even boot on it, no matter what the BIOS config was. Also, Vista wouldn't even recognize the SATA disks, even if the SATA ports were in IDE, RAID or AHCI modes (it requires a driver, even if you aren't doing RAID). -- I haven't used that MB but I am using a Gigabyte GA-P35-DS3L (core2) so I'll offer some general advice since no one else seems to want to! ;) I've had good luck with anything by Asus and Gigabyte. I tend to avoid boards with bleeding edge hardware/features as these will not have received so much testing (and may not even be supported) on FreeBSD. This in practice means get a board that's been on sale for a bit. None of my machines are configured for RAID but as a general point, most on this list use software RAID in the form of geom/geli/gmirror etc. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom.html The consensus seems to be that it's just as good as hardware raid performance-wise. There was a thread on this list about it a few months ago. I'd use FreeBSD 7.1-RC1 if I was building a FreeBSD machine today for production purposes as it will be more uptodate with respect drivers for newer hardware and most bugs will have been shaken out this close to release. My compatibilty check for hardware usually consists of going to Google and punching in FreeBSD and the name of the hardware. This usually brings up hits which indicate the level of support. HTH. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Vetting motherboard Gigabyte GA-MA78G-DS3H for FreeBSD 7.0-RELEASE
I'm currently looking for an ATX motherboard that supports the AM2+ socket, Phenom Quad-Core processor, 4 DDR2 RAM slots (800 MHz is fine), 6 SATA ports with RAID, and Gigabit LAN. Onboard VGA would be nice. It needs to work well with FreeBSD 7.0-RELEASE, using a 2-disk SATA RAID1. I'm currently looking at the Gigabyte GA-MA78G-DS3H. Has anyone successfully operated 7.0 on this board? Any booting issues? Did you need to modify the ISO to get it to boot (if so how)? Did RAID work? Did it require a special driver to be loaded (if so how)? Do any other motherboards fit the bill, given the specifications I give above? I recently got a black eye -( with the MSI K9N2G Neo-FD, using the GeForce 8200 (MCP78) chipset. FreeBSD 7.0-RELEASE and CentOS 5.2 wouldn't even boot on it, no matter what the BIOS config was. Also, Vista wouldn't even recognize the SATA disks, even if the SATA ports were in IDE, RAID or AHCI modes (it requires a driver, even if you aren't doing RAID). -- View this message in context: http://www.nabble.com/Vetting-motherboard-Gigabyte-GA-MA78G-DS3H-for-FreeBSD-7.0-RELEASE-tp21077043p21077043.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Vetting motherboard Gigabyte GA-MA78G-DS3H for FreeBSD 7.0-RELEASE
ThinkDifferently wrote: I'm currently looking for an ATX motherboard... Sorry, I forgot to mention that I do not need HTPC quality video and sound from this thing. I know the mobo I mentioned has HTPC written all over it, but it's the base qualities (processor, chipset, SATA, etc.) that really count. All I need is basic VGA, and some stereo sound wouldn't be too bad. I don't really care if accelerated video or theater-quality sound output was bad or flaky. I'm going to operate it as a server and plug it into a VGA KVM that has a max resolution of 1024x768. -- View this message in context: http://www.nabble.com/Vetting-motherboard-Gigabyte-GA-MA78G-DS3H-for-FreeBSD-7.0-RELEASE-tp21077043p21077407.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
Hell, Robert wrote: I just found a bug report for that issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=121423cat= Try asking on current@ - I think there were some patches available some time ago. -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 10. Dezember 2008 18:30 To: Hell, Robert Cc: freebsd-questions@freebsd.org Subject: Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
Hi,
I'm trying to run PostgreSQL 8.3 on a FreeBSD 7.0 amd64 server with more
than 2GB shared memory. The machine has 32GB RAM installed.
After setting kern.ipc.shmmax and kern.ipc.shmall to the appropriate
values, I still had no chance to start postgres with more than 2GB of
shared memory.
I wrote a small test which does the same as postgres: shmget and shmat:
#include sys/ipc.h
#include sys/shm.h
#include stdio.h
#include errno.h
int main()
{
int shmid, memKey = 1;
void *memAddress;
unsigned long size = 2147483648UL;
shmid = shmget(memKey, size, IPC_CREAT | IPC_EXCL);
if (shmid 0) {
printf(shmget failed: %d\n, errno);
return 1;
}
memAddress = shmat(shmid, NULL, 0);
if (memAddress == (void *) -1) {
printf(shmat failed: %d\n, errno);
}
return 0;
}
I found out that shmget failed with ENOMEM in shmget_allocate_segment
(sysv_shm.c) because of an overflow of size (requested shared memory in
bytes):
int i, segnum, shmid, size;
...
size = round_page(uap-size);
if (shm_committed + btoc(size) shminfo.shmall) {
return (ENOMEM);
}
When changing size to an unsigned long shmget works - but now shmat then
fails again with ENOMEM.
Is there any easy way to use a shared memory segment which is larger
than 2GB?
Kind regards,
Robert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
I just found a bug report for that issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=121423cat= Thanks, Robert -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 10. Dezember 2008 18:30 To: Hell, Robert Cc: freebsd-questions@freebsd.org Subject: Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 7.0 problems
I have just installed FreeBSD 7.0 on a laptop I just cleaned up. It used to run Fedora linux (I have a tv card which used to work on it, but now I can't get the drivers to work again), and it got very cluttered and started getting issues. The hardware is fine though- it just returned from servicing under warranty and nearly every component was replaced. Ergo I can't fault the hardware in any way. I tried FreeBSD 7.0 before, but it wasn't working properly for me and I didn't have the time then to get all the reports to make a PR. Now, I decided to sort this out- finally! The issues I'm having are similar to before, but not quite the same (keeping in mind that I didn't take much time with it before). They are: The wifi driver complains of timeout errors. (Intel iwi 2200bg - last time I tried had a ralink wifi) Xorg has DRI errors - fills /var and tries to kill the whole system (I'm probably exaggerating, but it felt like it at least) dhclient loses the IP constantly. So: How do I present these issues for review? What information is needed? Anything I've missed? This is the first time I've had to do this (which I think is pretty good- goes to show how well the OS is built), so I'm a little green in this regard. Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 problems
On Thursday 04 December 2008 03:06:34 Da Rock wrote: I have just installed FreeBSD 7.0 on a laptop I just cleaned up. It used to run Fedora linux (I have a tv card which used to work on it, but now I can't get the drivers to work again), and it got very cluttered and started getting issues. The hardware is fine though- it just returned from servicing under warranty and nearly every component was replaced. Ergo I can't fault the hardware in any way. I tried FreeBSD 7.0 before, but it wasn't working properly for me and I didn't have the time then to get all the reports to make a PR. Now, I decided to sort this out- finally! The issues I'm having are similar to before, but not quite the same (keeping in mind that I didn't take much time with it before). They are: The wifi driver complains of timeout errors. (Intel iwi 2200bg - last time I tried had a ralink wifi) Xorg has DRI errors - fills /var and tries to kill the whole system (I'm probably exaggerating, but it felt like it at least) dhclient loses the IP constantly. So: How do I present these issues for review? What information is needed? Anything I've missed? This is the first time I've had to do this (which I think is pretty good- goes to show how well the OS is built), so I'm a little green in this regard. For starters: * dmesg * pciconf -lv * if you have omni-positional antennas on the AP or not * if the dri problems go away when dri is disabled and no other symptoms show up * /var/log/Xorg.0.log without the abundance of dri errors * ls /var/db/pkg/ |grep 'xf86-video-*' * Why you installed 7.0 and not 7.1-BETA2 -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 problems
On Thursday 04 December 2008 19:51:59 Da Rock wrote: snip provided info Why would I install a beta when I'm mainly interested in stable releases? That's why I asked. You're not in a position to troubleshoot this problem, since the usual suspects (wrong driver, signs of significant acpi problems) don't apply and you'd have to really be willing to compile custom kernels, set tunables and apply patches to get to the bottom of this. The drm devices aren't created, and the reason for that is unclear. Nothing in dmesg shows a failure. The iwi problem could be signal strength, driver related or the fact that 7.0 uses SCHED_4BSD instead of the proven better working SCHED_ULE. And when reporting bugs in the PR system, the first thing developers will ask you is if you reproduce it on 7.1-BETA or a snapshot. Loads of fixes have gone into the upcoming 7.1. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 7.0: which distribution
If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
2008/12/2 Pieter Donche [EMAIL PROTECTED] On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? I never googled it before, but 2 sec gave me http://www.freebsd.org/releases/7.0R/hardware.html#PROC-AMD64 So use the amd64 ;) 368 vs 372 is that the 64 bit is compiled for 64 bit, and uses a little more space. what is 368 vs 372 ?? The size difference you talked about (368 vs 0.372) / Ebbe 2008/12/2 Pieter Donche [EMAIL PROTECTED] If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. 368 vs 372 is that the 64 bit is compiled for 64 bit, and uses a little more space. / Ebbe 2008/12/2 Pieter Donche [EMAIL PROTECTED] If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, 2 Dec 2008, Ebbe Hjorth wrote: 2008/12/2 Pieter Donche [EMAIL PROTECTED] On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. I never googled it before, but 2 sec gave me http://www.freebsd.org/releases/7.0R/hardware.html#PROC-AMD64 So use the amd64 ;) Is the amd64 distribution mature enough, as compared to the i386? Aren't there any problems to be expected to arrive, months after initial install and way in the production usage ?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
So use the amd64 ;) Is the amd64 distribution mature enough, as compared to the i386? yes Aren't there any problems to be expected to arrive, months after initial install and way in the production usage ?? no. the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, 2 Dec 2008, Wojciech Puchar wrote: the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ia64 is itanium. you need amd64. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0: which distribution
the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? Nvidia!!! Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.12/1824 - Release Date: 2-12-2008 9:31 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nvidia (Re: FreeBSD 7.0: which distribution)
Johan Hendriks wrote: the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? Nvidia!!! I am one ot these folks, using 32-bit FreeBSD on my desktop, just because of Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? Regards, O.K. -- Testi oma Interneti kiirust / Test Your Internet speed: http://speedtest.zzz.ee/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nvidia (Re: FreeBSD 7.0: which distribution)
=?windows-1250?Q?Ott_K=F6stner?= writes: I am one ot these folks, using 32-bit FreeBSD on my desktop, just because of Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? For the same reason they don't provide up-to-date i386 drivers. This is a recurring thread; please search the mailing list archives. (Hint: try Zander nvidia as a search term.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia (Re: FreeBSD 7.0: which distribution)
Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? because there are not enough pressure from clients? (by not buying them) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? 368 vs 372 is that the 64 bit is compiled for 64 bit, and uses a little more space. what is 368 vs 372 ?? / Ebbe 2008/12/2 Pieter Donche [EMAIL PROTECTED] If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Nvidia (Re: FreeBSD 7.0: which distribution)
Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? because there are not enough pressure from clients? (by not buying them) They missing some things in the kernel of FreeBSD so it has nothing to do with nvidia not willing it is FreeBSD who lacks support in the kernel for a 64bit NVIDIA driver. But like said before there are numoures threads about this. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.12/1824 - Release Date: 2-12-2008 9:31 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, Dec 2, 2008 at 4:59 PM, Johan Hendriks [EMAIL PROTECTED] wrote: the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? Nvidia!!! No Nvidia on that particular motherboard so the OP is on the safe side. @OP: I have just installed FBSD amd 64 2 weeks ago to benefit of +4 GB of RAM and until now i didn't have any kind of problem in compiling and running applications. My box is a web/mail/vpn/router/samba (yes i know there shouldn't be that many services on the box, but tell my boss that) and all the apps are working like a charm. v Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.12/1824 - Release Date: 2-12-2008 9:31 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
My box is a web/mail/vpn/router/samba (yes i know there shouldn't be that many services on the box, but tell my boss that) and all the apps are working like a charm. his money his problem. overspending on hardware it's quite common, instead of paying more employees with the same money. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
Pieter Donche wrote: On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? No -- ia64 is the Itanium chip. Use amd64 for Xeons -- it covers all recent multi-core Intel chips as well as the AMD 64bit processors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0: which distribution
Pieter Donche wrote: On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? No -- ia64 is the Itanium chip. Use amd64 for Xeons -- it covers all recent multi-core Intel chips as well as the AMD 64bit processors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0: which distribution
Pieter Donche wrote: On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? No -- ia64 is the Itanium chip. Use amd64 for Xeons -- it covers all recent multi-core Intel chips as well as the AMD 64bit processors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
compat libs in FreeBSD 7.0
Hi What happened to the compatibility libraries in FreeBSD 7.0 release Need to run some FreeBSD-5.4 binaries on a 7.0 System. Can't find the libs any longer Mats ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compat libs in FreeBSD 7.0
Mats Lindberg [EMAIL PROTECTED] writes: Hi What happened to the compatibility libraries in FreeBSD 7.0 release Need to run some FreeBSD-5.4 binaries on a 7.0 System. Can't find the libs any longer Try ports: misc/compat5x -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 fdisk issue during installation
for each bootable system.If it already has some MS thing loaded, I use some tool such as Gparted or Partition Magic to shrink the MS primary partition and create two or three or four of them. Then I use fdisk to set up the FreeBSD slice to be bootable and bsdlabel to partition that slice. By the way, 'dual boot' is kind of a generic term referring to any number of bootable slices more than one. So, it could refer to two, three or four actual bootable systems on the drive. Except for something like the hidden Dell diagnostic slice (HP and probably other vendors like to do that as well), MS must be in the first slice because it doesn't like to play well with other systems. But, it does overlook the 'hidden' slices OK. That 'hidden' attribute is ignored by FreeBSD. But, since it doesn't care which slice it is in, that is no problem. When I have a second (or third, etc) disk on the machine, I generally do not make those disks bootable. I make them just one plain slice each and generally, since they mostly get used as mass data storage, I create just one partition in that slice. But, I have created more when it was useful. One I am thinking about, it was useful to make more partitions in the second drive because I was using it to build a system to distribute to other machines and I could isolate that in one separate partition that way and use other partitionss for development space. If you have more than one drive and you want to put some bootable slices on each of them, you can do that by putting an MBR on each one, marking each slice you want bootable as such and putting the boot block and OS on that drive. It is a little a little confusing that there is a Master Boot Record and a boot block being named in such similar sounding ways. They are each one sector long and are quite related, but are different and both are needed. To boot, the system turns control over to the BIOS. The BIOS does a bunch of stuff with the hardware and then looks for an MBR in its list of boot devices (which you can normally configure in BIOS control utility. You usually have to break out of the boot sequence early on to get in to BIOS) The BIOS loads the first MBR it finds and then transfers control to it. The MBR does some minor housekeeping and then looks for slices that are marked bootable in its boot table (set by fdisk). It also looks to see it there is another disk down the line with its own MBR. The MBR makes up a little menu of slices on its own disk and the next drive with an MBR, if any. Either you select one from the menu or let it take its default. Then the MBR marks that slice as the latest(current) one booted, loads up the boot block and transfers control to it. The boot block does some housekeeping and causes the system to start. If you select that next MBR, it does just like the first - lists its own bootable slices and a possible next MBR, then loads up what you select and transfers control. You can chain bootable disk this way. If either the disk's MBR or that slice's boot block are bad in some way, the boot fails. Generally, nowdays, most systems commit a whole track to the MBR and the boot block rather than just the single sector that is officially called for. The other sectors are just ignored/wasted. It is a trivial amount to waste. The main reason for doing so (I think) is it is easier to calculate the addressing on even track or cylinder boundaries rather than one sector off. But, because of this, there are several third party MBRs out there that assume that space will be available and so they use it to create fancier MBRs and boot blocks, with more elaborate menu and such. That is nice, but in reality, they ultimately still do exactly what the basic MBRs and boot blocks do.Grub is one of the most well known of these extended MBRs. FreeBSD has taken the attitude of being strict about the standard so it can work with all systems and limits itself to the one sector MBR and bootblocks. I have heard some talk of making a FreeBSD version of extended MBRs and bootblocks, but I don't know if anyone is really doing it. jerry Appreciate the clarification Cheers Jona On Fri, Nov 21, 2008 at 8:55 PM, Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Nov 21, 2008 at 08:03:58PM +0100, Jonatan Evald Buus wrote: Greetings, I tried to install FreeBSD 7.0 on an old server earlier today and ran in to a number of issues related to slicing and labeling the disk using fdisk. The drive in the machine is a 40GB Seagate Barracude (ST34001A) installed as a Secondary Master on the IDE bus using LBA. The BIOS reports that the drive has 16 sectors pr block, but little else. When accessing fdisk during install, fdisk complains that the disk geometry is invalid and sets it to the default geometry for 40GB: Cylinders: 4865 Heads: 255
problem with IPCS on (FreeBSD 7.0-RELEASE-p5)
FreeBSD 7.0-RELEASE-p5 amd64
Programming C/C++.
The down Queues (msgid = msgget ) after message reception (msgrcv)
# ipcs
Message Queues:
T ID KEY MODEOWNERGROUP
q 327680 1174 --rw-rw-rw- rootwheel
.
Example:
msgserv.c
---
#include stdio.h
#include stdlib.h
#include sys/types.h
#include sys/ipc.h
#include sys/msg.h
#include string.h
#include sys/errno.h
#include msgtypes.h
int main(int argc, char * argv[])
{
struct msg_t message;
int msgid;
char * response = Ok!;
msgid = msgget(KEY, 0666 | IPC_CREAT);
msgrcv(msgid, message, sizeof(message), 2, 0);
/*
ATTENTION!!!
After msgrcv(msgid, message, sizeof(message), 2, 0); -
Queues(msgid) DOWN
Helps only to create anew msgid = msgget(KEY, 0666 | IPC_CREAT);
*/
printf(Client (pid = %i) sent: %s, message.snd_pid, message.body);
message.mtype = 1;
message.snd_pid = getpid();
strcpy(message.body, response);
msgsnd(msgid, message, sizeof(message), 0);
// errno = 22 (bad msgid)
msgrcv(msgid, message, sizeof(message), 2, 0);
msgctl(msgid, IPC_RMID, 0);
return EXIT_SUCCESS;
}
---
msgtypes.h
---
#ifndef MSG_TYPES
#define MSG_TYPES
#define KEY 1174
#define MAXLEN 512
struct msg_t
{
long mtype;
int snd_pid;
char body[MAXLEN];
};
#endif
---
msgcli.c
---
#include stdio.h
#include stdlib.h
#include sys/types.h
#include sys/ipc.h
#include sys/msg.h
#include strings.h
#include msgtypes.h
int main(int argc, char * argv[])
{
int msgid;
int i;
struct msg_t message;
char buf[MAXLEN];
msgid = msgget(KEY, 0666);
if (msgid == -1)
{
printf(Server is not running!\n, msgid);
return EXIT_FAILURE;
}
i = 0;
while ( (i (MAXLEN - 1)) ((message.body[i++] = getchar()) !=
'\n') );
message.body[i] = '\0';
message.mtype = 2;
message.snd_pid = getpid ();
msgsnd(msgid, message, sizeof(message), 0);
msgrcv(msgid, message, sizeof(message), 1, 0);
printf(Server (pid= %i) responded: %s\n, message.snd_pid,
message.body);
message.mtype = 2;
msgsnd(msgid, message, sizeof(message), 0);
return EXIT_SUCCESS;
}
---
Tested on FreeBSD 6.2 i386 - All has passed remarkably, errors were not
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsd 7.0 - asterisk 1.4 install problem (libslang-1.4.9 conflicts with installed package(s):,libslang2-2.1.4 )
OS: FreeBSD 7.0-RELEASE-p5 (i386) Asterisk: 1.4.21.2_5 I dont wanna install old version asterisk ( /usr/ports/net/asterisk12). ## # pwd /usr/ports/net/asterisk # make === Vulnerability check disabled, database not found === Found saved configuration for asterisk-1.4.21.2_4 === Extracting for asterisk-1.4.21.2_5 = MD5 Checksum OK for asterisk-1.4.21.2.tar.gz. = SHA256 Checksum OK for asterisk-1.4.21.2.tar.gz. = MD5 Checksum OK for asterisk-1.4.21.1-codec-negotiation-20080715.diff.gz. = SHA256 Checksum OK for asterisk-1.4.21.1-codec-negotiation-20080715.diff.gz. /bin/mkdir -p /usr/ports/net/asterisk/work/asterisk-1.4.21.2/codecs/ilbc /usr/bin/find /usr/ports/net/asterisk/work/asterisk-1.4.21.2 -name '*.d' -delete === Patching for asterisk-1.4.21.2_5 === Applying distribution patches for asterisk-1.4.21.2_5 === Applying extra patch /usr/ports/net/asterisk/files/ilbc_enable.diff === Applying extra patch /usr/ports/net/asterisk/files/codecnego-patch-Makefile === Applying extra patch /usr/ports/net/asterisk/files/dtmf_debug.diff === Applying extra patch /usr/ports/net/asterisk/files/feature_disconnect.diff === Applying extra patch /usr/ports/net/asterisk/files/sip_force_callid.diff === Applying extra patch /usr/ports/net/asterisk/files/sip_set_auth.diff === Applying extra patch /usr/ports/net/asterisk/files/rtp_force_dtmf-codecnego.diff === Applying FreeBSD patches for asterisk-1.4.21.2_5 /usr/bin/sed -i.bak -e 's|/var/lib|/usr/local/share|g' /usr/ports/net/asterisk/work/asterisk-1.4.21.2/configs/musiconhold.conf.sample === asterisk-1.4.21.2_5 depends on executable: mpg123 - found === asterisk-1.4.21.2_5 depends on executable: gmake - found === asterisk-1.4.21.2_5 depends on executable: bison - found === asterisk-1.4.21.2_5 depends on shared library: speex.1 - found === asterisk-1.4.21.2_5 depends on shared library: newt.51 - not found === Verifying install for newt.51 in /usr/ports/devel/newt === newt-0.51.0_7 depends on shared library: slang.1 - not found === Verifying install for slang.1 in /usr/ports/devel/libslang === Installing for libslang-1.4.9 === libslang-1.4.9 conflicts with installed package(s): libslang2-2.1.4 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/devel/libslang. *** Error code 1 Stop in /usr/ports/devel/newt. *** Error code 1 Stop in /usr/ports/net/asterisk. *** Error code 1 Stop in /usr/ports/net/asterisk. ### # whereis libslang libslang: /usr/ports/devel/libslang # cd /usr/ports/devel/libslang # make # make install === Installing for libslang-1.4.9 === libslang-1.4.9 conflicts with installed package(s): libslang2-2.1.4 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/devel/libslang. *** Error code 1 Stop in /usr/ports/devel/libslang. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 7.0 fdisk issue during installation
Greetings, I tried to install FreeBSD 7.0 on an old server earlier today and ran in to a number of issues related to slicing and labeling the disk using fdisk. The drive in the machine is a 40GB Seagate Barracude (ST34001A) installed as a Secondary Master on the IDE bus using LBA. The BIOS reports that the drive has 16 sectors pr block, but little else. When accessing fdisk during install, fdisk complains that the disk geometry is invalid and sets it to the default geometry for 40GB: Cylinders: 4865 Heads: 255 Sectors: 63 I've tried with the following configuration based on what was reported by the BIOS: Cylinders: 19150 Heads: 255 Sectors: 16 Looking in the manual: http://www.seagate.com/support/disc/manuals/ata/cuda7200pm.pdf, Seagate is specifying the following logical characteristic: Cylinders: 16383 Read / Write heads: 16 Sectors pr track: 63 Which of these settings should be the correct one for the fdisk geometry? Additionally I encountered problems during installation if splitting the disk into more than 4 slices. This would cause the following error to be thrown during prior to the install files being copied (when sysinstall was executing the newfs commands): Error mounting /mnt/dev/X on /mnt/usr. No such file or directory Using only 4 slices seems to have solved this error, however I'd like the disk layout to use 5 slices as follows: / = 512MB swap = 2048MB (the machine has 1024MB RAM) /tmp = 512MB /var = 2048MB /usr = whatever remains I noticed that when having 5 slices, the last slice (/usr) would be named X rather than ad2s5 as I'd expect (the drive was detected as ad2). Is this behaviour related to the error in any way? Also, is the above disk layout good for a server intended to run both a web server (Apache) and a database server (PostGreSQL) ? Finally after installation (using only 4 slices) the system will only boot if the FreeBSD boot manager is used. This in turn causes a 4 menu options, all of them named FreeBSD to appear during startup despite only the / slice having been set as bootable in fdisk which appears to be indicated by an A in the flag column. Selecting the first menu item by pressing F1 will make the system boot as expected. It seems rather silly though to use a boot manager when FreeBSD is the only operating system that is installed (and ever will be installed) on the machine. If the FreeBSD boot manager is not used however and only the MBR is set during installation, the system will fail at startup with error Invalid Partition Table. Is this because the harddrive is installed as the Secondary Master on the IDE bus? Appreciate any input on this Cheers Jona ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 fdisk issue during installation
On Fri, Nov 21, 2008 at 08:03:58PM +0100, Jonatan Evald Buus wrote: Greetings, I tried to install FreeBSD 7.0 on an old server earlier today and ran in to a number of issues related to slicing and labeling the disk using fdisk. The drive in the machine is a 40GB Seagate Barracude (ST34001A) installed as a Secondary Master on the IDE bus using LBA. The BIOS reports that the drive has 16 sectors pr block, but little else. When accessing fdisk during install, fdisk complains that the disk geometry is invalid and sets it to the default geometry for 40GB: Cylinders: 4865 Heads: 255 Sectors: 63 I've tried with the following configuration based on what was reported by the BIOS: Cylinders: 19150 Heads: 255 Sectors: 16 Looking in the manual: http://www.seagate.com/support/disc/manuals/ata/cuda7200pm.pdf, Seagate is specifying the following logical characteristic: Cylinders: 16383 Read / Write heads: 16 Sectors pr track: 63 Which of these settings should be the correct one for the fdisk geometry? Let the system set it and just go with what it does. Geometry is virtual nowdays. Except in some unusual situations (on IDE) Cylinders, heads and sectors most often do not mean what they used to. The system drivers have it all figured out. The important thing for you is the total number of blocks/sectors. If that doesn't work, you will have to do some diagnosis, but in about 10 out of 9 times, accepting how FreeBSD sets it is correct and works. Additionally I encountered problems during installation if splitting the disk into more than 4 slices. This would cause the following error to be thrown during prior to the install files being copied (when sysinstall was executing the newfs commands): You cannot have more than 4 slices. The system limits you to 4 slices, identified by numbers 1..4 Once you divide in to slices, each can be further divided in to up to 8 partitions, although it is really 7 because partition 'c' has special meaning and is not really available to be a real partition. Partitions are identified with alpha letters a..h - with 'c' being used to identify the whole slice. You use fdisk to create the slices (and write the MBR and set the bootable flag). Then you use bsdlabel (formerly called disklabel) to create the partitions within a slice (plus write the slice boot block. Typically, you want to make partition 'a' be the root (/) filesystem and 'b' be swap space on a bootable system slice. Some things assume these designations. Then you newfs partitions a, d, e, f, g, h or as many as you use. But don't touch c and don't newfs b if it is to be swap. jerry Error mounting /mnt/dev/X on /mnt/usr. No such file or directory Using only 4 slices seems to have solved this error, however I'd like the disk layout to use 5 slices as follows: / = 512MB swap = 2048MB (the machine has 1024MB RAM) /tmp = 512MB /var = 2048MB /usr = whatever remains I noticed that when having 5 slices, the last slice (/usr) would be named X rather than ad2s5 as I'd expect (the drive was detected as ad2). Is this behaviour related to the error in any way? Also, is the above disk layout good for a server intended to run both a web server (Apache) and a database server (PostGreSQL) ? Finally after installation (using only 4 slices) the system will only boot if the FreeBSD boot manager is used. That is probably because you have created what is referred to in the documentation as a dangerously dedicated disk. You can make it work that way. FreeBSD can handle it. But other systems will not play nicely with it. This in turn causes a 4 menu options, all of them named FreeBSD to appear during startup despite only the / slice having been set as bootable in fdisk which appears to be indicated by an A in the flag column. Again, because you tried to do it the wrong way. You created 4 FreeBSD slices, probably each with an MBR and so the BIOS and the first MBR think they are all bootable. Selecting the first menu item by pressing F1 will make the system boot as expected. It seems rather silly though to use a boot manager when FreeBSD is the only operating system that is installed (and ever will be installed) on the machine. You can put in the other non-boot manager block during installation if you want and it will only boot FreeBSD. But, something is needed. I forget what they call it in the sysinstall screen, but you might just as well put in the FreeBSD boot manager (MBR). If the FreeBSD boot manager is not used however and only the MBR is set during installation, the system will fail at startup with error Invalid Partition Table. Is this because the harddrive is installed as the Secondary Master on the IDE bus? No, it is because you did not create any partition table (with bsdlabel). jerry Appreciate any input on this Cheers Jona ___ freebsd-questions@freebsd.org mailing list http
Re: FreeBSD 7.0 fdisk issue during installation
Hi Jerry, Thank you for the swift and very thorough response. If I understand you correctly, then I should only create 1 slice of the entire disk (seeing as FreeBSD will be the only OS) using fdisk and then partition the slice using bsdlabels from sysinstall? Previously I was aiming for 5 slices, each of which had a single partition as described below. From your explanation I take it that slices are what Windows refers to as Primary Partitions? If that's the case then I understand the behaviour I experienced. Is it possible to make a slice non-bootable? And would there be any benefits (less fragmentation, faster access time etc.) in using slices rather than partitions to layout the harddrive or should slices only be used to represent a physical harddrive? Appreciate the clarification Cheers Jona On Fri, Nov 21, 2008 at 8:55 PM, Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Nov 21, 2008 at 08:03:58PM +0100, Jonatan Evald Buus wrote: Greetings, I tried to install FreeBSD 7.0 on an old server earlier today and ran in to a number of issues related to slicing and labeling the disk using fdisk. The drive in the machine is a 40GB Seagate Barracude (ST34001A) installed as a Secondary Master on the IDE bus using LBA. The BIOS reports that the drive has 16 sectors pr block, but little else. When accessing fdisk during install, fdisk complains that the disk geometry is invalid and sets it to the default geometry for 40GB: Cylinders: 4865 Heads: 255 Sectors: 63 I've tried with the following configuration based on what was reported by the BIOS: Cylinders: 19150 Heads: 255 Sectors: 16 Looking in the manual: http://www.seagate.com/support/disc/manuals/ata/cuda7200pm.pdf, Seagate is specifying the following logical characteristic: Cylinders: 16383 Read / Write heads: 16 Sectors pr track: 63 Which of these settings should be the correct one for the fdisk geometry? Let the system set it and just go with what it does. Geometry is virtual nowdays. Except in some unusual situations (on IDE) Cylinders, heads and sectors most often do not mean what they used to. The system drivers have it all figured out. The important thing for you is the total number of blocks/sectors. If that doesn't work, you will have to do some diagnosis, but in about 10 out of 9 times, accepting how FreeBSD sets it is correct and works. Additionally I encountered problems during installation if splitting the disk into more than 4 slices. This would cause the following error to be thrown during prior to the install files being copied (when sysinstall was executing the newfs commands): You cannot have more than 4 slices. The system limits you to 4 slices, identified by numbers 1..4 Once you divide in to slices, each can be further divided in to up to 8 partitions, although it is really 7 because partition 'c' has special meaning and is not really available to be a real partition. Partitions are identified with alpha letters a..h - with 'c' being used to identify the whole slice. You use fdisk to create the slices (and write the MBR and set the bootable flag). Then you use bsdlabel (formerly called disklabel) to create the partitions within a slice (plus write the slice boot block. Typically, you want to make partition 'a' be the root (/) filesystem and 'b' be swap space on a bootable system slice. Some things assume these designations. Then you newfs partitions a, d, e, f, g, h or as many as you use. But don't touch c and don't newfs b if it is to be swap. jerry Error mounting /mnt/dev/X on /mnt/usr. No such file or directory Using only 4 slices seems to have solved this error, however I'd like the disk layout to use 5 slices as follows: / = 512MB swap = 2048MB (the machine has 1024MB RAM) /tmp = 512MB /var = 2048MB /usr = whatever remains I noticed that when having 5 slices, the last slice (/usr) would be named X rather than ad2s5 as I'd expect (the drive was detected as ad2). Is this behaviour related to the error in any way? Also, is the above disk layout good for a server intended to run both a web server (Apache) and a database server (PostGreSQL) ? Finally after installation (using only 4 slices) the system will only boot if the FreeBSD boot manager is used. That is probably because you have created what is referred to in the documentation as a dangerously dedicated disk. You can make it work that way. FreeBSD can handle it. But other systems will not play nicely with it. This in turn causes a 4 menu options, all of them named FreeBSD to appear during startup despite only the / slice having been set as bootable in fdisk which appears to be indicated by an A in the flag column. Again, because you tried to do it the wrong way. You created 4 FreeBSD slices, probably each with an MBR and so the BIOS and the first MBR think they are all bootable. Selecting the first menu
Re: FreeBSD 7.0 fdisk issue during installation
On Fri, 21 Nov 2008 22:41:07 +0100, Jonatan Evald Buus [EMAIL PROTECTED] wrote: If I understand you correctly, then I should only create 1 slice of the entire disk (seeing as FreeBSD will be the only OS) using fdisk and then partition the slice using bsdlabels from sysinstall? Yes, that's the usual way. Sysinstall suggest this way, too, but you can use fdisk and bsdlabel manually, if you want. Previously I was aiming for 5 slices, each of which had a single partition as described below. Not neccessary, as you see. By the way, if you would want to have one disk (harddisk) for your home directories, you wouldn't make any slice on it, you could create just one partition there, for example: /dev/ad0s1b = swap /dev/ad0s1a = / /dev/ad0s1d = /tmp /dev/ad0s1e = /var /dev/ad0s1f = /usr /dev/ad2= /home From your explanation I take it that slices are what Windows refers to as Primary Partitions? Yes. If that's the case then I understand the behaviour I experienced. You understood it correctly. Is it possible to make a slice non-bootable? Yes, by not setting the bootable flag in the slice editor. And would there be any benefits (less fragmentation, faster access time etc.) in using slices rather than partitions to layout the harddrive or should slices only be used to represent a physical harddrive? I don't think it will give you any speed gains when you have, let's say, /dev/ad[0s[12345]c instead of /dev/ad0s1[adefg]. Speed limitations usually occur according to the order harddisks are placed on the (P)ATA bus and how you copy data from one partition to another, for example, a master - slave copy usually is slower than a master - master copy; copies between partitions on the same drive tend to be slower than copies between two physical drives. In daily use, I don't think your suggestion would be of a significant benefit - if it was, it would have been done this way for years already. :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 fdisk issue during installation
that way and use other partitionss for development space. If you have more than one drive and you want to put some bootable slices on each of them, you can do that by putting an MBR on each one, marking each slice you want bootable as such and putting the boot block and OS on that drive. It is a little a little confusing that there is a Master Boot Record and a boot block being named in such similar sounding ways. They are each one sector long and are quite related, but are different and both are needed. To boot, the system turns control over to the BIOS. The BIOS does a bunch of stuff with the hardware and then looks for an MBR in its list of boot devices (which you can normally configure in BIOS control utility. You usually have to break out of the boot sequence early on to get in to BIOS) The BIOS loads the first MBR it finds and then transfers control to it. The MBR does some minor housekeeping and then looks for slices that are marked bootable in its boot table (set by fdisk). It also looks to see it there is another disk down the line with its own MBR. The MBR makes up a little menu of slices on its own disk and the next drive with an MBR, if any. Either you select one from the menu or let it take its default. Then the MBR marks that slice as the latest(current) one booted, loads up the boot block and transfers control to it. The boot block does some housekeeping and causes the system to start. If you select that next MBR, it does just like the first - lists its own bootable slices and a possible next MBR, then loads up what you select and transfers control. You can chain bootable disk this way. If either the disk's MBR or that slice's boot block are bad in some way, the boot fails. Generally, nowdays, most systems commit a whole track to the MBR and the boot block rather than just the single sector that is officially called for. The other sectors are just ignored/wasted. It is a trivial amount to waste. The main reason for doing so (I think) is it is easier to calculate the addressing on even track or cylinder boundaries rather than one sector off. But, because of this, there are several third party MBRs out there that assume that space will be available and so they use it to create fancier MBRs and boot blocks, with more elaborate menu and such. That is nice, but in reality, they ultimately still do exactly what the basic MBRs and boot blocks do.Grub is one of the most well known of these extended MBRs. FreeBSD has taken the attitude of being strict about the standard so it can work with all systems and limits itself to the one sector MBR and bootblocks. I have heard some talk of making a FreeBSD version of extended MBRs and bootblocks, but I don't know if anyone is really doing it. jerry Appreciate the clarification Cheers Jona On Fri, Nov 21, 2008 at 8:55 PM, Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Nov 21, 2008 at 08:03:58PM +0100, Jonatan Evald Buus wrote: Greetings, I tried to install FreeBSD 7.0 on an old server earlier today and ran in to a number of issues related to slicing and labeling the disk using fdisk. The drive in the machine is a 40GB Seagate Barracude (ST34001A) installed as a Secondary Master on the IDE bus using LBA. The BIOS reports that the drive has 16 sectors pr block, but little else. When accessing fdisk during install, fdisk complains that the disk geometry is invalid and sets it to the default geometry for 40GB: Cylinders: 4865 Heads: 255 Sectors: 63 I've tried with the following configuration based on what was reported by the BIOS: Cylinders: 19150 Heads: 255 Sectors: 16 Looking in the manual: http://www.seagate.com/support/disc/manuals/ata/cuda7200pm.pdf, Seagate is specifying the following logical characteristic: Cylinders: 16383 Read / Write heads: 16 Sectors pr track: 63 Which of these settings should be the correct one for the fdisk geometry? Let the system set it and just go with what it does. Geometry is virtual nowdays. Except in some unusual situations (on IDE) Cylinders, heads and sectors most often do not mean what they used to. The system drivers have it all figured out. The important thing for you is the total number of blocks/sectors. If that doesn't work, you will have to do some diagnosis, but in about 10 out of 9 times, accepting how FreeBSD sets it is correct and works. Additionally I encountered problems during installation if splitting the disk into more than 4 slices. This would cause the following error to be thrown during prior to the install files being copied (when sysinstall was executing the newfs commands): You cannot have more than 4 slices. The system limits you to 4 slices, identified by numbers 1..4 Once you divide in to slices, each can be further divided in to up to 8 partitions, although it is really 7 because
Re: PEA kernel in FreeBSD 7.0
Olivier Nicole wrote: Hi, I am about to install few brand new servers, each with 8GB RAM. If I choose to use 7.0, will I have to use PEA kernel to be able to access the total memory? Yes if you want to use the 32-bit version of FreeBSD. Use a 64-bit version instead. signature.asc Description: OpenPGP digital signature
