Re: 8.0-RC3 Available

2009-11-13 Thread Chao Shin

Hi All,

Is sysinstall can work now?
After I set Label in sysinstall it has message come out said
"Unable to find device node for /dev/ad4s1b in /dev!
The creation of filesystems will be aborted."
and installation aborted.

I have installed freebsd with sysinstall ten years, that is first time I
meet that



The third and hopefully last of the Release Candidates for the FreeBSD
8.0 release cycle is now available.  Unless something catastrophic comes
up within the next couple of days we will begin the final builds for
8.0-RELEASE.

There is one known issue with the igb(4) driver we are still deciding
whether or not to fix as part of 8.0-RELEASE versus doing an Errata
Notice for it some time after the release is out.  It has been patched
in head, and the SVN commit for it is r199192.  If any of you are able
to give that patch a try on a machine with the igb(4) NIC it would be
appreciated.

If you notice problems you can report them through the normal Gnats PR
system or on the freebsd-current mailing list.  I do cross-post
announcements to freebsd-stable because this particular release is
"about to become a stable branch" but when it comes to watching for
issues related to the release most of the developers pay more attention
to the freebsd-current list.

ISO images for all supported architectures are available on the FTP
sites, and a "memory stick" image is available for amd64/i386
architectures.  For amd64/i386 architectures the cdrom and memstick
images include the documentation packages but no other packages.  The
DVD image includes the packages that will probably be available on the
official release media but is subject to change between now and release.
For sparc64 there is now a livefs cdrom, disc1 includes the
documentation packages, and the DVD image has the set of packages that
currently build for sparc64 (which is a sub-set of the set provided for
amd64/i386).

If you are using csup/cvsup methods to update an older system the branch
tag to use is RELENG_8_0.

The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.0-RELEASE,
7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, 8.0-BETA4,
8.0-RC1 or 8.0-RC2 can upgrade as follows:
# freebsd-update upgrade -r 8.0-RC3
During this process, FreeBSD Update may ask the user to help by merging
some configuration files or by confirming that the automatically
performed merging was done correctly.  Systems running 8.0-BETA3 may
print the warning

INDEX-OLD.all: Invalid arguments

when downloading updates; this warning is a harmless bug (fixed in
8.0-BETA4) and can be safely ignored.

# freebsd-update install
The system must be rebooted with the newly installed kernel before  
continuing.

# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components:

# freebsd-update install
At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or
earlier will be prompted by freebsd-update to rebuild all third-party
applications (e.g., ports installed from the ports tree) due to updates
in system libraries.  See:

http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html

for mode details.  After updating installed third-party applications
(and again, only if freebsd-update printed a message indicating that
this was necessary), run freebsd-update again so that it can delete the
old (no longer used) system libraries:

# freebsd-update install
Finally, reboot into 8.0-RC3:
# shutdown -r now

MD5/SHA256 checksums for the image files:

MD5 (8.0-RC3-amd64-bootonly.iso) = 641881caa82ea85c118bc15fff12fce6
MD5 (8.0-RC3-amd64-disc1.iso) = 854c273b89792cd0366d5399df1034eb
MD5 (8.0-RC3-amd64-dvd1.iso) = 9bd1bb2507bc2a3037bc321bb2724bd6
MD5 (8.0-RC3-amd64-livefs.iso) = c5f427c8bf823e10a5348935cec2d7ee
MD5 (8.0-RC3-amd64-memstick.img) = 6af9e213914a58a5779715ae5882bd25

MD5 (8.0-RC3-i386-bootonly.iso) = dfaec92ae358ab780d317aa66482ca9e
MD5 (8.0-RC3-i386-disc1.iso) = 460f6cfddaebee6ae59a7d5f73695246
MD5 (8.0-RC3-i386-dvd1.iso) = 98d3f65f2444a8745f787df5ce9e1f0c
MD5 (8.0-RC3-i386-livefs.iso) = 5184b7f6403d1d24991533bde0e580ff
MD5 (8.0-RC3-i386-memstick.img) = 8774ef1d6bdf541e440f2f8ed22a2493

MD5 (8.0-RC3-ia64-bootonly.iso) = fd0af8f34937cf7fc78ea0063252afb7
MD5 (8.0-RC3-ia64-disc1.iso) = 96313c25e53fc333c258ed675007f3d7
MD5 (8.0-RC3-ia64-disc2.iso) = 235714607a2805c396ece829839405be
MD5 (8.0-RC3-ia64-disc3.iso) = 53fca9243ccc788190ca58d24f363cbe
MD5 (8.0-RC3-ia64-dvd1.iso) = 4e24736ab50bc2227c72dbeab6869266
MD5 (8.0-RC3-ia64-livefs.iso) = b6d76cf77ed714631bf714ff78b8e950

MD5 (8.0-RC3-pc98-bootonly.iso) = 137d17ec3830b6ae831b6fb48adf86e0
MD5 (8.0-RC3-pc98-disc1.iso) = 3624b1f7b3a659a7454718e38b9a1ee0
MD5 (8.0-RC3-pc98-livefs.iso) = 29ed3786b2df1c2e72e45d1187f3e788
MD5 (8.0-RC3-powerpc-bootonly.iso) = e7d8508639dee4aed5e52a24d6e27b69
MD5 (8.0-RC3-powerpc-disc1.iso) = 1016ae7753db153b7be0f5d167f595b9
MD5 (8.0-RC3-power

Re: 8.0-RC3 Available

2009-11-13 Thread Chao Shin

Hi All,

Is sysinstall can work now?
After I set Label in sysinstall it has message come out said
"Unable to find device node for /dev/ad4s1b in /dev!
The creation of filesystems will be aborted."
and installation aborted.

I have installed freebsd with sysinstall ten years, that is first time I
meet that

my box is dell's optiplex 745, I've installed 7.2R on it without any  
problem

before.



The third and hopefully last of the Release Candidates for the FreeBSD
8.0 release cycle is now available.  Unless something catastrophic comes
up within the next couple of days we will begin the final builds for
8.0-RELEASE.

There is one known issue with the igb(4) driver we are still deciding
whether or not to fix as part of 8.0-RELEASE versus doing an Errata
Notice for it some time after the release is out.  It has been patched
in head, and the SVN commit for it is r199192.  If any of you are able
to give that patch a try on a machine with the igb(4) NIC it would be
appreciated.

If you notice problems you can report them through the normal Gnats PR
system or on the freebsd-current mailing list.  I do cross-post
announcements to freebsd-stable because this particular release is
"about to become a stable branch" but when it comes to watching for
issues related to the release most of the developers pay more attention
to the freebsd-current list.

ISO images for all supported architectures are available on the FTP
sites, and a "memory stick" image is available for amd64/i386
architectures.  For amd64/i386 architectures the cdrom and memstick
images include the documentation packages but no other packages.  The
DVD image includes the packages that will probably be available on the
official release media but is subject to change between now and release.
For sparc64 there is now a livefs cdrom, disc1 includes the
documentation packages, and the DVD image has the set of packages that
currently build for sparc64 (which is a sub-set of the set provided for
amd64/i386).

If you are using csup/cvsup methods to update an older system the branch
tag to use is RELENG_8_0.

The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.0-RELEASE,
7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, 8.0-BETA4,
8.0-RC1 or 8.0-RC2 can upgrade as follows:
# freebsd-update upgrade -r 8.0-RC3
During this process, FreeBSD Update may ask the user to help by merging
some configuration files or by confirming that the automatically
performed merging was done correctly.  Systems running 8.0-BETA3 may
print the warning

INDEX-OLD.all: Invalid arguments

when downloading updates; this warning is a harmless bug (fixed in
8.0-BETA4) and can be safely ignored.

# freebsd-update install
The system must be rebooted with the newly installed kernel before  
continuing.

# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components:

# freebsd-update install
At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or
earlier will be prompted by freebsd-update to rebuild all third-party
applications (e.g., ports installed from the ports tree) due to updates
in system libraries.  See:

http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html

for mode details.  After updating installed third-party applications
(and again, only if freebsd-update printed a message indicating that
this was necessary), run freebsd-update again so that it can delete the
old (no longer used) system libraries:

# freebsd-update install
Finally, reboot into 8.0-RC3:
# shutdown -r now

MD5/SHA256 checksums for the image files:

MD5 (8.0-RC3-amd64-bootonly.iso) = 641881caa82ea85c118bc15fff12fce6
MD5 (8.0-RC3-amd64-disc1.iso) = 854c273b89792cd0366d5399df1034eb
MD5 (8.0-RC3-amd64-dvd1.iso) = 9bd1bb2507bc2a3037bc321bb2724bd6
MD5 (8.0-RC3-amd64-livefs.iso) = c5f427c8bf823e10a5348935cec2d7ee
MD5 (8.0-RC3-amd64-memstick.img) = 6af9e213914a58a5779715ae5882bd25

MD5 (8.0-RC3-i386-bootonly.iso) = dfaec92ae358ab780d317aa66482ca9e
MD5 (8.0-RC3-i386-disc1.iso) = 460f6cfddaebee6ae59a7d5f73695246
MD5 (8.0-RC3-i386-dvd1.iso) = 98d3f65f2444a8745f787df5ce9e1f0c
MD5 (8.0-RC3-i386-livefs.iso) = 5184b7f6403d1d24991533bde0e580ff
MD5 (8.0-RC3-i386-memstick.img) = 8774ef1d6bdf541e440f2f8ed22a2493

MD5 (8.0-RC3-ia64-bootonly.iso) = fd0af8f34937cf7fc78ea0063252afb7
MD5 (8.0-RC3-ia64-disc1.iso) = 96313c25e53fc333c258ed675007f3d7
MD5 (8.0-RC3-ia64-disc2.iso) = 235714607a2805c396ece829839405be
MD5 (8.0-RC3-ia64-disc3.iso) = 53fca9243ccc788190ca58d24f363cbe
MD5 (8.0-RC3-ia64-dvd1.iso) = 4e24736ab50bc2227c72dbeab6869266
MD5 (8.0-RC3-ia64-livefs.iso) = b6d76cf77ed714631bf714ff78b8e950

MD5 (8.0-RC3-pc98-bootonly.iso) = 137d17ec3830b6ae831b6fb48adf86e0
MD5 (8.0-RC3-pc98-disc1.iso) = 3624b1f7b3a659a7454718e38b9a1ee0
MD5 (8.0-RC3-pc98-livefs.iso) = 29ed3786b2df1c2e72e45d1187f3e788
MD5 (8.0-RC3-powerpc-bootonly.iso) = e7d8508639dee4aed5e52a24d6e27

Re: 8.0-RC3 Available

2009-11-13 Thread Chao Shin

在 Fri, 13 Nov 2009 16:42:44 +0800,Chao Shin  写道:


Hi All,

Is sysinstall can work now?
After I set Label in sysinstall it has message come out said
"Unable to find device node for /dev/ad4s1b in /dev!
The creation of filesystems will be aborted."
and installation aborted.

I have installed freebsd with sysinstall ten years, that is first time I
meet that



I found the reason of that. I've fdisk that disk with dd mode before, the
sysinstall can't overwrite the partition record, so can't label on it.
If I want to install 8.0-rc3 on that disk, I have to erase the partition
record with "dd if=/dev/zero of=/dev/ad4 bs=1M count=1" before  
installation.



--
The Power to Serve
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: 8.0-RC3 Available

2009-11-13 Thread Jeremy Chadwick


On Fri, Nov 13, 2009 at 05:25:54PM +0800, Chao Shin wrote:
> ??? Fri, 13 Nov 2009 16:42:44 +0800???Chao Shin  ??:
> 
> >Hi All,
> >
> >Is sysinstall can work now?
> >After I set Label in sysinstall it has message come out said
> >"Unable to find device node for /dev/ad4s1b in /dev!
> >The creation of filesystems will be aborted."
> >and installation aborted.
> >
> >I have installed freebsd with sysinstall ten years, that is first time I
> >meet that
> >
> 
> I found the reason of that. I've fdisk that disk with dd mode before, the
> sysinstall can't overwrite the partition record, so can't label on it.
> If I want to install 8.0-rc3 on that disk, I have to erase the partition
> record with "dd if=/dev/zero of=/dev/ad4 bs=1M count=1" before
> installation.

I've covered this (indirectly) on my blog, documenting that 8.0-RC1's
sysinstall "was not doing the right thing" with regards to setting up
disks to be fully compatible with the new GEOM improvements.  The result
was a disk that would work, but GEOM would complain about the disk label
not matching geometry.

http://koitsu.wordpress.com/2009/10/12/testing-out-freebsd-8-0-rc1/

8.0-RC2 addressed this by fixing sysinstall to do the Right Thing for
new installs.  Existing installs, however, will be susceptible to the
problem.  Note the difference in the disk label between an 8.0-RC1 and
8.0-RC2 system here:

http://koitsu.wordpress.com/2009/11/02/testing-out-freebsd-8-0-rc2/

Finally, I'll note that your dd command is horribly excessive.  All you
need to do is nuke the MBR + PBR and you're good to go.  The following
should be sufficient:

dd if=/dev/zero of=/dev/adX count=5

-- 
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: how to mirror cvs or svn with rsync

2009-11-13 Thread Wout Decré
Hello

Maybe the following article will get you started:

http://www.freebsd.org/doc/en/articles/hubs/

Kind regards

Wout

On Fri, 2009-11-13 at 00:39 +0300, Nikolay Tychina wrote:
> Hi everybody!
> 
> How do I mirror FreeBSD sources (CVS or SVN) with rsync?
> This is the first time I have to use rsync, and its man page really makes me
> confused.
> I would really appreciate your help.
> 
> Regards,
> 
> Nik
> ___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-www
> To unsubscribe, send any mail to "freebsd-www-unsubscr...@freebsd.org"
> 


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: hald running 100%

2009-11-13 Thread Dan Langille

Adam Vande More wrote:
On Thu, Nov 12, 2009 at 7:59 PM, Dan Langille > wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

After upgrading to 8.0-PRERELEASE today, I'm seeing hald at 100% on both
my laptop and my desktop:


 PID USERNAME  THR PRI NICE   SIZERES STATE  C   TIME   WCPU COMMAND
1500 haldaemon   1 1180 22944K  4904K CPU1   1 107:44 100.00% hald

uptime was about 1:50 at this point.

Seems to be relatively common from the posts I've seen.


ThinkPad X61s.  dmesg output attached.  FWIW.


it's not a common issue anymore.  What version of hal are you running 
and did you recompile after the upgrade?


I don't know the version (laptop is not available just now) but I will 
recompile.  That's the next task.  Thanks.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[libdispatch-dev] FreeBSD 8-STABLE now supports GCD, libdispatch port updated (fwd)

2009-11-13 Thread Robert Watson


FYI to FreeBSD 8-STABLE followers who may be interested in using Apple's GCD 
technology on FreeBSD.  GCD, for those who may have missed it, is a concurrent 
programming framework introdued in Mac OS X Snow Leopard, now also supported 
on FreeBSD.


There are a number of useful links on the wiki page, but this provides the 
best high-level introduction:


  
http://images.apple.com/macosx/technology/docs/GrandCentral_TB_brief_20090903.pdf

My announcement text (and wiki link) below.

Robert N M Watson
Computer Laboratory
University of Cambridge

-- Forwarded message --
Date: Fri, 13 Nov 2009 12:21:40 + (GMT)
From: Robert Watson 
To: libdispatch-...@lists.macosforge.org
Subject: [libdispatch-dev] FreeBSD 8-STABLE now supports GCD,
libdispatch port updated


Dear all:

Just an FYI that all the parts are now in place to use GCD (libdispatch) on 
FreeBSD 8-STABLE.  You will need the following:


- FreeBSD 8-STABLE snapshot from at least 2009-11-01 (r198732)
- FreeBSD libdispatch port from at least 2009-11-11

Do the upgrade to the 8-STABLE snapshot first so that the port can find the 
required kernel features.  As a reminder, you can find FreeBSD/GCD port status, 
quick start guide, and general information here:


  http://wiki.freebsd.org/GCD

I have updated it to reflect 8.x support.  Thanks are due to Stacey Son and 
Stanislav Sedov for their work to make this happen!


Robert N M Watson
Computer Laboratory
University of Cambridge
___
libdispatch-dev mailing list
libdispatch-...@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD 7.x hang-on-boot on Dell 1950

2009-11-13 Thread Richard Tector

Zaphod Beeblebrox wrote:

I have a dell 1950 here on the floor.  Since "1950" seems to refer to a lot
of things with a lot of configurations, I'm going to attempt to narrow that
down a bit.

It's got 2x 2.33Ghz dual core pentiums (stepping 06-0F-6 according to the
bios) in it and it has an SAS RAID card that FreeBSD recognises.  I've
upgraded the BIOS to 2.6.1.  It has two SAS 70G drives in a RAID 1
configuration and it has a DVD (although it will only boot from CDs).

If it helps, it's between 2 and 3 years old, I think.

If I allow the machine to boot normally, it stopps after checking the floppy
(there is no floppy) with the following message:

fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: does not respond
device_attach: fdc0 attach returned 6

If I boot the machine without ACPI, it seems to stop at the same place
(stopping after having checked the ata controller, which checks right before
the floppy)

If I boot the machine verbose, I get no more information --- it stopps at
the same place.

I have tried this (so far) with 7.2-R and 7.1-R.  Both do the same thing.
  

Can you try with 7.0 (should be available on ftp-archive)?

I have a 1950 from Sept '07 that's now running 7.2-STABLE i386 with the 
fd devices removed. It started out as 7.0-RELEASE, so maybe its a 
problem introduced since then?


Also, you didn't mention if you were running i386 or amd64.

Richard
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Fwd: hald running 100%

2009-11-13 Thread M. Vale
-- Forwarded message --
From: M. Vale 
Date: 2009/11/13
Subject: Re: hald running 100%
To: Dan Langille 




2009/11/13 Dan Langille 

Adam Vande More wrote:
>
>> On Thu, Nov 12, 2009 at 7:59 PM, Dan Langille > d...@langille.org>> wrote:
>>
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>After upgrading to 8.0-PRERELEASE today, I'm seeing hald at 100% on
>> both
>>my laptop and my desktop:
>>
>>
>> PID USERNAME  THR PRI NICE   SIZERES STATE  C   TIME   WCPU
>> COMMAND
>>1500 haldaemon   1 1180 22944K  4904K CPU1   1 107:44 100.00% hald
>>
>>uptime was about 1:50 at this point.
>>
>>Seems to be relatively common from the posts I've seen.
>>
>>
>>ThinkPad X61s.  dmesg output attached.  FWIW.
>>
>>
>> it's not a common issue anymore.  What version of hal are you running and
>> did you recompile after the upgrade?
>>
>
> I don't know the version (laptop is not available just now) but I will
> recompile.  That's the next task.  Thanks.
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>

Hi Dan, I've found the problem.

The problem is that FreeBSD 7.x installs libusb but in 8.0 libusb is already
in the kernel and hald behaves badly don't know why.

But i've removed the port libusb from my system, recompiled hald and now
everything works ok :)

Best Regards

Mauro V.

Edit: Ups forgot to add cc to FreeBSD Stable
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Ext firewire drive not mounted after update

2009-11-13 Thread Robert
Greetings

I just now finished an upgrade to 8.0 Prerelease vie csup, buildworld,
make kernel (generic), reboot, mergemaster -p, installworld,
mergemaster -Ui, reboot again. 

[rob...@asus64] ~> uname -a
FreeBSD asus64.shasta204.local 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE
#7: Fri Nov 13 12:01:35 PST 2009
r...@asus64.shasta204.local:/usr/obj/usr/src/sys/GENERIC  amd64

I have a WD external 500G mybook connected via firewire. It has worked
fine since 6.something through 7.x and all of the betas and rc's up to
this point.

I use the drive for backups of all the computers on my network. Booting
into multi-user will fail because the drive is not found. I had to
comment it out of fstab in order to boot multi-user. 

If I unplug the firewire cable I get this message on the console:

Nov 13 12:42:15 asus64 kernel: fwohci0: fwohci_intr_core: BUS reset
Nov 13 12:42:15 asus64 kernel: fwohci0: fwohci_intr_core:
node_id=0x, SelfID Count=2, CYCLEMASTER mode Nov 13 12:42:15
asus64 kernel: firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0)  (me)
Nov 13 12:42:15 asus64 kernel: firewire0: bus manager 0 Nov 13 12:42:16
asus64 kernel: firewire0: fw_attach_dev:Removing missing device
ID:0090a991e0013e57

Plugging the cable back in gives this:

Nov 13 12:42:21 asus64 kernel: fwohci0: fwohci_intr_core: BUS reset
Nov 13 12:42:21 asus64 kernel: fwohci0: fwohci_intr_core:
node_id=0x0001, SelfID Count=3, CYCLEMASTER mode Nov 13 12:42:21
asus64 kernel: firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1)  (me)
Nov 13 12:42:21 asus64 kernel: firewire0: bus manager 1 Nov 13 12:42:21
asus64 kernel: firewire0: New S800 device ID:0090a991e0013e57

No device is created in /dev/da*

I did not see anything in /usr/src/UPDATING and I do not recall
anything like this in the mail lists (currect or stable). 

Did I miss something or is this a regression? /var/run/dmesg.boot and
pciconf -lv attached. I can provide anything else needed.

TIA

Robert

dmesg.boot
Description: Binary data
no...@pci0:0:0:0:   class=0x05 card=0x81bf1043 chip=0x02f110de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Host Bridge'
class  = memory
subclass   = RAM
no...@pci0:0:0:1:   class=0x05 card=0x81bf1043 chip=0x02fa10de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Memory Controller 0'
class  = memory
subclass   = RAM
no...@pci0:0:0:2:   class=0x05 card=0x81bf1043 chip=0x02fe10de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Memory Controller 1'
class  = memory
subclass   = RAM
no...@pci0:0:0:3:   class=0x05 card=0x81bf1043 chip=0x02f810de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Memory Controller 5'
class  = memory
subclass   = RAM
no...@pci0:0:0:4:   class=0x05 card=0x81bf1043 chip=0x02f910de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Memory Controller 4'
class  = memory
subclass   = RAM
no...@pci0:0:0:5:   class=0x05 card=0x81bf1043 chip=0x02ff10de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Host Bridge'
class  = memory
subclass   = RAM
no...@pci0:0:0:6:   class=0x05 card=0x81bf1043 chip=0x027f10de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Memory Controller 3'
class  = memory
subclass   = RAM
no...@pci0:0:0:7:   class=0x05 card=0x81bf1043 chip=0x027e10de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'C51 Memory Controller 2'
class  = memory
subclass   = RAM
pc...@pci0:0:2:0:   class=0x060400 card=0x10de chip=0x02fc10de rev=0xa1 
hdr=0x01
vendor = 'Nvidia Corp'
device = 'C51 PCIe Bridge'
class  = bridge
subclass   = PCI-PCI
pc...@pci0:0:3:0:   class=0x060400 card=0x10de chip=0x02fd10de rev=0xa1 
hdr=0x01
vendor = 'Nvidia Corp'
device = 'C51 PCIe Bridge'
class  = bridge
subclass   = PCI-PCI
pc...@pci0:0:4:0:   class=0x060400 card=0x10de chip=0x02fb10de rev=0xa1 
hdr=0x01
vendor = 'Nvidia Corp'
device = 'C51 PCIe Bridge'
class  = bridge
subclass   = PCI-PCI
vgap...@pci0:0:5:0: class=0x03 card=0x81bf1043 chip=0x024210de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'NVIDIA GeForce 6100 (unknown)'
class  = display
subclass   = VGA
no...@pci0:0:9:0:   class=0x05 card=0x81c01043 chip=0x027010de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'MCP51 Host Bridge'
class  = memory
subclass   = RAM
is...@pci0:0:10:0:  class=0x060100 card=0x81c01043 chip=0x026110de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Corp'
device = 'MCP51 LPC Bridge'
class  = bridge
subclass   = PCI-ISA
nfs...@pci0:0:10:1: class=0x0c0500 card=0x81c01043 chip=0x026410de rev=0xa2 
hdr=0x00
vendor = 'Nvidia Cor

Re: (MORE INFO) Ext firewire drive not mounted after update

2009-11-13 Thread Dan Nelson
In the last episode (Nov 13), Robert said:
> On Fri, 13 Nov 2009 13:01:47 -0800
> Robert  wrote:
> 
> In the time honored FreeBSD tradition, I am replying to my own email. 
> 
> I booted with a 8.0RC2 livefs CD and the external disk shows up as
> /dev/da0, /das1, /das1d.  I then connected the external drive via USB and
> rebooted to the 8.0 Prerelease system.  The drive shows up and is able to
> mount.
> 
> It appears that some thing is amiss with the latest version. I will
> download the latest livefs iso and see if that works.

I think I remember seing a posting within the last few days saying that the
"sbp" device wan't going to be compiled into the 8.0-release kernel due to
it causing hangs on boot.  If you run "kldload sbp" as root after the system
has booted you should see your disk devices appear.

I can't find the list post mentioning it, but here's the svn commit log:


r199112 | kensmith | 2009-11-09 15:39:42 -0600 (Mon, 09 Nov 2009) | 11 lines

Changed paths:
   M /stable/8/sys/amd64/conf/GENERIC
   M /stable/8/sys/i386/conf/GENERIC
   M /stable/8/sys/ia64/conf/GENERIC
   M /stable/8/sys/powerpc/conf/GENERIC
   M /stable/8/sys/sparc64/conf/GENERIC

Comment out the sbp(4) entry for GENERIC config files that contain it. 
There are known issues with this driver that are beyond what can be fixed
for 8.0-RELEASE and the bugs can cause boot failure on some systems.  It's
not clear if it impacts all systems and there is interest in getting the
problem fixed so for now just comment it out instead of remove it.

Commit straight to stable/8, this is an 8.0-RELEASE issue.  Head was left
alone so work on it can continue there.

Reviewed by:Primary misc. architecture maintainers (marcel, marius)


-- 
Dan Nelson
dnel...@allantgroup.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: (MORE INFO) Ext firewire drive not mounted after update

2009-11-13 Thread Robert
On Fri, 13 Nov 2009 13:01:47 -0800
Robert  wrote:

In the time honored FreeBSD tradition, I am replying to my own email. 

I booted with a 8.0RC2 livefs CD and the external disk shows up
as /dev/da0, /das1, /das1d. I then connected the external drive via USB
and rebooted to the 8.0 Prerelease system. The drive shows up and is
able to mount.

It appears that some thing is amiss with the latest version. I will
download the latest livefs iso and see if that works.

Robert
 
> Greetings
> 
> I just now finished an upgrade to 8.0 Prerelease vie csup, buildworld,
> make kernel (generic), reboot, mergemaster -p, installworld,
> mergemaster -Ui, reboot again. 
> 
> [rob...@asus64] ~> uname -a
> FreeBSD asus64.shasta204.local 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE
> #7: Fri Nov 13 12:01:35 PST 2009
> r...@asus64.shasta204.local:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> I have a WD external 500G mybook connected via firewire. It has worked
> fine since 6.something through 7.x and all of the betas and rc's up to
> this point.
> 
> I use the drive for backups of all the computers on my network.
> Booting into multi-user will fail because the drive is not found. I
> had to comment it out of fstab in order to boot multi-user. 
> 
> If I unplug the firewire cable I get this message on the console:
> 
> Nov 13 12:42:15 asus64 kernel: fwohci0: fwohci_intr_core: BUS reset
> Nov 13 12:42:15 asus64 kernel: fwohci0: fwohci_intr_core:
> node_id=0x, SelfID Count=2, CYCLEMASTER mode Nov 13 12:42:15
> asus64 kernel: firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0)  (me)
> Nov 13 12:42:15 asus64 kernel: firewire0: bus manager 0 Nov 13
> 12:42:16 asus64 kernel: firewire0: fw_attach_dev:Removing missing
> device ID:0090a991e0013e57
> 
> Plugging the cable back in gives this:
> 
> Nov 13 12:42:21 asus64 kernel: fwohci0: fwohci_intr_core: BUS reset
> Nov 13 12:42:21 asus64 kernel: fwohci0: fwohci_intr_core:
> node_id=0x0001, SelfID Count=3, CYCLEMASTER mode Nov 13 12:42:21
> asus64 kernel: firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1)  (me)
> Nov 13 12:42:21 asus64 kernel: firewire0: bus manager 1 Nov 13
> 12:42:21 asus64 kernel: firewire0: New S800 device ID:0090a991e0013e57
> 
> No device is created in /dev/da*
> 
> I did not see anything in /usr/src/UPDATING and I do not recall
> anything like this in the mail lists (currect or stable). 
> 
> Did I miss something or is this a regression? /var/run/dmesg.boot and
> pciconf -lv attached. I can provide anything else needed.
> 
> TIA
> 
> Robert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: how to mirror cvs or svn with rsync

2009-11-13 Thread Doug Barton
First off, please don't cross post. If you are not sure where to
direct a question, the freebsd-questi...@freebsd.org list should be
your first step.

Nikolay Tychina wrote:
> Hi everybody!
> 
> How do I mirror FreeBSD sources (CVS or SVN) with rsync?
> This is the first time I have to use rsync, and its man page really makes me
> confused.
> I would really appreciate your help.

It would be easier to answer your question if you were more clear
about what your goal is. What is it that you are trying to accomplish?


Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: (MORE INFO) Ext firewire drive not mounted after update

2009-11-13 Thread Robert
On Fri, 13 Nov 2009 17:15:39 -0600
Dan Nelson  wrote:

> In the last episode (Nov 13), Robert said:
> > On Fri, 13 Nov 2009 13:01:47 -0800
> > Robert  wrote:
> >
> > 
> > It appears that some thing is amiss with the latest version. I will
> > download the latest livefs iso and see if that works.
> 
> I think I remember seing a posting within the last few days saying
> that the "sbp" device wan't going to be compiled into the 8.0-release
> kernel due to it causing hangs on boot.  If you run "kldload sbp" as
> root after the system has booted you should see your disk devices
> appear.
> 
> I can't find the list post mentioning it, but here's the svn commit
> log:

Dan

Thanks for responding. I checked and the "sbp" device is in fact
commented out. I do remember a thread a month or two back about some
folkes having trouble with firewire drives. I never experiem=nced any
trouble on of that trouble on this system. 

I can continue to operate my drive on USB but I may need firewire in the
near future. I have a friend who is a photographer and I archive her
photos for her. She sends me an external drive or two and I burn
her projects onto DVD. I am not sure if her drives have an USB
connector.

I guess I will cross that bridge when I come to it.

Thanks again for the prompt response. If anyone needs me to test
possible fixes for this, I am willing and available.  Cheap too :-)

Robert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD 7.x hang-on-boot on Dell 1950

2009-11-13 Thread Zaphod Beeblebrox
On Fri, Nov 13, 2009 at 9:30 AM, Richard Tector <
richardtec...@thekeelecentre.com> wrote:

>
> Can you try with 7.0 (should be available on ftp-archive)?
>

I can confirm that 7.0 exhibits the same behaviour (and is incidentally very
chatty about probing the raid controller)


> I have a 1950 from Sept '07 that's now running 7.2-STABLE i386 with the fd
> devices removed. It started out as 7.0-RELEASE, so maybe its a problem
> introduced since then?
>
> Also, you didn't mention if you were running i386 or amd64.


This 1950 may predate that a bit, but I'm not sure how to nail it down
exactly, other than by it's hardware components.  Anyways, 7.0 does the same
thing --- still wedged.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD 7.x hang-on-boot on Dell 1950

2009-11-13 Thread Jeremy Chadwick
On Fri, Nov 13, 2009 at 08:57:56PM -0500, Zaphod Beeblebrox wrote:
> On Fri, Nov 13, 2009 at 9:30 AM, Richard Tector <
> richardtec...@thekeelecentre.com> wrote:
> 
> > Can you try with 7.0 (should be available on ftp-archive)?
> 
> I can confirm that 7.0 exhibits the same behaviour (and is incidentally very
> chatty about probing the raid controller)
> 
> 
> > I have a 1950 from Sept '07 that's now running 7.2-STABLE i386 with the fd
> > devices removed. It started out as 7.0-RELEASE, so maybe its a problem
> > introduced since then?
> >
> > Also, you didn't mention if you were running i386 or amd64.
> 
> This 1950 may predate that a bit, but I'm not sure how to nail it down
> exactly, other than by it's hardware components.  Anyways, 7.0 does the same
> thing --- still wedged.

I haven't seen anyone recommend this as a test method yet -- disabling
fdc prior to the kernel booting via the loader prompt:

- Press 6 at the menu,
- At the loader prompt, type:

  set hint.fdc.0.disabled="1"
  boot -v   (or without -v; your choice)

You shouldn't need to set hint.fd.0.disabled="1", since fd0 would
normally bind to fdc0; disable the latter and you disable the lesser.

The intention here is to rule out the device attachment failures from
fdc as the source of the deadlock.

For sake of comparison, on our systems (non-Dell), this is what we see
during fdc/fd probe and shortly after:

fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
cpu0:  on acpi0

I'd have recommended disabling ACPI but you tried it already with the
same results.  :-)

-- 
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"