Joseph Olatt wrote:
Hello,
I have the following SATA controller card on my system that appears to
be unsupported by FreeBSD 7-STABLE. Does anybody know if this card is
supported or will be supported in the near future?
[EMAIL PROTECTED]:0:14:0: class=0x010485 card=0x01371025 chip=0x07f810d
On Sun, Sep 21, 2008 at 09:57:04PM +0200, Torfinn Ingolfsen wrote:
> Hi,
>
> The last part of last year and earlier this year a patch for if_re was
> needed to get it working reliably on my machine[1] (and some others).
> Now I have upgraded this machine to FreeBSD 6.4-prerelease, more info
On Sat, Sep 20, 2008 at 09:45:10AM -0500, Bob Willcox wrote:
> On Sat, Sep 20, 2008 at 07:04:56AM -0700, Jeremy Chadwick wrote:
> > On Sat, Sep 20, 2008 at 08:24:29AM -0500, Bob Willcox wrote:
[...]
> > > [EMAIL PROTECTED]:2:0:0: class=0x02 card=0xe0001458 chip=0x816810ec
> > > rev=0x02
On Sep 21, Jeremy Chadwick wrote:
> The tool is behaving how it should. Try using the -a flag.
Ok, I feel dumb now :)
Thanks,
-Clint
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
On Sun, Sep 21, 2008 at 05:40:40PM -0700, Clint Olsen wrote:
> On Sep 21, Jeremy Chadwick wrote:
> > With regards to this specific item: can you provide the full smartctl
> > command you're using (including device), and all of the output? I have
> > an idea of what the problem is, but I'd need to
On Sep 21, Jeremy Chadwick wrote:
> With regards to this specific item: can you provide the full smartctl
> command you're using (including device), and all of the output? I have
> an idea of what the problem is, but I'd need to see the output first.
# smartctl /dev/ad6
smartctl version 5.38 [i38
On Sun, Sep 21, 2008 at 04:59:50PM -0700, Clint Olsen wrote:
> > Also, are there any kernel messages about ATA/SCSI disk errors or other
> > anomalies?
>
> None. In fact smartctl will not do anything now. It just prints out the
> quick banner message and exits immediately with no error.
With re
On Sep 21, Jeremy Chadwick wrote:
> You could also consider using clri(8) to clear the inode (190). Do this
> in single-user while the filesystem is not mounted. After using clri,
> run fsck a couple times.
Booting single-user and running fsck again seems to have corrected these
errors. For som
On Sep 21, Jeremy Chadwick wrote:
> Re-adding mailing list to the CC list.
>
> No, I don't think that is the case, assuming the filesystems are UFS2
> and are using softupdates. When booting multi-user, fsck is run in the
> background, meaning the system is fully up + usable even before the fsck
On Sun, Sep 21, 2008 at 04:06:33PM -0700, Jason C. Wells wrote:
> Jason C. Wells wrote:
>> Jason C. Wells wrote:
>
>> I should add that 'systcl security.jail.chflags_allowed=1' allowed
>> installworld to proceed without error. That solves my immediate
>> problem. There appears to be a bug in th
On Mon, Sep 22, 2008 at 01:47:06AM +0300, yusuf özbilgin wrote:
> ata8-master --> ata8 --> atapci1
> and atapci1 is Intel Ahci Controller.
> I used GENERIC conf file and recompile the kernel but the problem is still
> exist. (I am using freebsd7)
Before you rebuilt the kernel, did you update /usr
Jason C. Wells wrote:
Jason C. Wells wrote:
I should add that 'systcl security.jail.chflags_allowed=1' allowed
installworld to proceed without error. That solves my immediate problem.
There appears to be a bug in the security mechanism.
The reason there appeared to be a bug in the security
ata8-master --> ata8 --> atapci1
and atapci1 is Intel Ahci Controller.
I used GENERIC conf file and recompile the kernel but the problem is still
exist. (I am using freebsd7)
Then I added IDE disk to the system The system didnt detect the ide disk.
This mainboard is G33 chipset Intel mainboar
Jason C. Wells wrote:
Jeremy Chadwick wrote:
On Sun, Sep 21, 2008 at 11:17:58AM -0700, Jason C. Wells wrote:
I have the problem similar to one described in 20071024 UPDATING.
The build is running inside a jail. The system is 6.2-RELEASE. I
supped this moring. I have the correct lib/Makefil
Jeremy Chadwick wrote:
On Sun, Sep 21, 2008 at 11:17:58AM -0700, Jason C. Wells wrote:
I have the problem similar to one described in 20071024 UPDATING. The
build is running inside a jail. The system is 6.2-RELEASE. I supped this
moring. I have the correct lib/Makefile. During installworld
On Sun, Sep 21, 2008 at 02:59:30PM -0700, Clint Olsen wrote:
> I ran in multi-user mode because the system booted. I figured that it
> would have halted the boot if it was serious enough to warrant single-user
> mode fsck. That has happened before.
>
> Thanks,
>
> -Clint
>
> On Sep 21, Jeremy C
On Sun, Sep 21, 2008 at 02:34:26PM -0700, Clint Olsen wrote:
> Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190
> Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE
> INCONSISTENCY; RUN fsck MANUALLY.
>
> Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix
On Sun, Sep 21, 2008 at 11:17:58AM -0700, Jason C. Wells wrote:
> I have the problem similar to one described in 20071024 UPDATING. The
> build is running inside a jail. The system is 6.2-RELEASE. I supped this
> moring. I have the correct lib/Makefile. During installworld I receive
> an e
On Sun, Sep 21, 2008 at 09:57:15AM -0500, Bob Willcox wrote:
> On Sat, Sep 20, 2008 at 01:50:24PM -0500, Bob Willcox wrote:
> > On Sat, Sep 20, 2008 at 08:05:33AM -0700, Jeremy Chadwick wrote:
> > > On Sat, Sep 20, 2008 at 09:45:10AM -0500, Bob Willcox wrote:
> > > > On Sat, Sep 20, 2008 at 07:04:5
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY;
RUN fsck MANUALLY.
Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix
whatever to the questions posed as fsck runs. What does this all mean?
On Sun, Sep 21, 2008 at 1:22 PM, Robert Watson <[EMAIL PROTECTED]> wrote:
> On Sat, 20 Sep 2008, Vlad GALU wrote:
>
>> Will the zero-copy bpf(4) changes be merged to the stable branch before
>> the release?
>
> Dear Vlad:
>
> Unfortunately, no. The code seems stable in 8-CURRENT, but I don't feel
Hi,
The last part of last year and earlier this year a patch for if_re was
needed to get it working reliably on my machine[1] (and some others).
Now I have upgraded this machine to FreeBSD 6.4-prerelease, more info
here [2].
Are the if_re patches included in FreeBSD 6.4-prerelease now, or are
they
I have the problem similar to one described in 20071024 UPDATING. The
build is running inside a jail. The system is 6.2-RELEASE. I supped this
moring. I have the correct lib/Makefile. During installworld I receive
an error:
install: /lib/libc.so.6: chflags: Operation not permitted
*** Error
Byung-Hee HWANG wrote:
> in my experience, in usual kernel && userland upgrading is good,
> however, everytime port upgrading have problem, whenever new -REL is
> released ;; i usually do port upgrading by portupgrade(1).
>
> at once(when 6.2-REL was released) i did upgrading port by
> portupgrade
On Sun, 2008-09-21 at 09:48 -0700, Doug Barton wrote:
> Byung-Hee HWANG wrote:
> > in my experience, in usual kernel && userland upgrading is good,
> > however, everytime port upgrading have problem, whenever new -REL is
> > released ;; i usually do port upgrading by portupgrade(1).
> >
> > at onc
On Sun, 21 Sep 2008 06:45:29 -0700
Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> Remove "device udbp" from your kernel configuration and try again.
> The problem with bulk pipes is somewhat well-known at this point.
This machine have a GENERIC kernel:
[EMAIL PROTECTED] uname -a
FreeBSD kg-work2.kg
On Sun, 21 Sep 2008 12:44:03 +0200
Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote:
> I will try ufdformat on a different machine now.
Ok, on a different machine[1], it works without problems:
[EMAIL PROTECTED] uname -a
FreeBSD kg-i82.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #3: Wed May 28 15:59:38
CEST
On Sat, Sep 20, 2008 at 9:52 PM, Aristedes Maniatis <[EMAIL PROTECTED]> wrote:
>
> On 21/09/2008, at 10:34 AM, netgeek wrote:
>
>> Perhaps there is a middle ground here? What about a statement that each
>> major branch (6.x, 7.x) will be supported for at least 24+ months from its
>> last productio
On Sat, Sep 20, 2008 at 01:50:24PM -0500, Bob Willcox wrote:
> On Sat, Sep 20, 2008 at 08:05:33AM -0700, Jeremy Chadwick wrote:
> > On Sat, Sep 20, 2008 at 09:45:10AM -0500, Bob Willcox wrote:
> > > On Sat, Sep 20, 2008 at 07:04:56AM -0700, Jeremy Chadwick wrote:
> > > > On Sat, Sep 20, 2008 at 08:
On Sun, 21 Sep 2008, Mario Sergio Fujikawa Ferreira wrote:
I've been running FreeBSD 7.0-STABLE from August 1 without problems.
I tried updating to the latest -STABLE but I got a system panic.
Hi Mario--
This is a known problem, and will hopefully be resolved shortly. In essence,
the v4
On Sat, Sep 20, 2008 at 10:30:43PM -0700, Brian wrote:
> Brian wrote:
>> The board in question is an Asus M3A78-EMH HDMI. I have tried the
>> instructions for a safe kernel compile in /usr/src/updating also.
>> Even after that, the kernel starts to load, but the root partition
>> cant be fo
On Sun, Sep 21, 2008 at 04:47:57AM +0300, yusuf özbilgin wrote:
> I added kernel configuration as attachment.
>
> When I boot system via freebsd live cd
>
> at boot process
>
>
> hptrr: no controller detected.
> acd0:DVDR at ata2-master UDMA66
> ad16: 476938MB at ata8-master SATA300
>
On Sun, Sep 21, 2008 at 12:44:03PM +0200, Torfinn Ingolfsen wrote:
> On Thu, 18 Sep 2008 23:33:40 +0100
> "Bruce M. Simpson" <[EMAIL PROTECTED]> wrote:
>
> > Someone was going to pick this up, finish it off, and commit it, but
> > I haven't heard back from them:
> > http://people.freebsd.org/~bms
Mario Sergio Fujikawa Ferreira wrote:
On Sun, Sep 21, 2008 at 11:48:19AM +0100, Kris Kennaway wrote:
Mario Sergio Fujikawa Ferreira wrote:
Hi,
I've been running FreeBSD 7.0-STABLE from August 1 without problems.
I tried updating to the latest -STABLE but I got a system panic.
panic:
On Sun, Sep 21, 2008 at 11:48:19AM +0100, Kris Kennaway wrote:
> Mario Sergio Fujikawa Ferreira wrote:
> > Hi,
> >
> > I've been running FreeBSD 7.0-STABLE from August 1 without problems.
> >
> > I tried updating to the latest -STABLE but I got a system panic.
> >
> >
> > panic: _rw_rlo
Mario Sergio Fujikawa Ferreira wrote:
Hi,
I've been running FreeBSD 7.0-STABLE from August 1 without problems.
I tried updating to the latest -STABLE but I got a system panic.
panic: _rw_rlock (udpinp): wlock already held @
/usr/src/sys/netinet/udp_usrreq.c
FreeBSD 7.1-PRERELEA
On Thu, 18 Sep 2008 23:33:40 +0100
"Bruce M. Simpson" <[EMAIL PROTECTED]> wrote:
> Someone was going to pick this up, finish it off, and commit it, but
> I haven't heard back from them:
> http://people.freebsd.org/~bms/dump/tools/ufdformat/
It compiled fine on FreeBSD 7.0-stable:
[EMAIL PROTECTE
Hi,
I've been running FreeBSD 7.0-STABLE from August 1 without problems.
I tried updating to the latest -STABLE but I got a system panic.
panic: _rw_rlock (udpinp): wlock already held @
/usr/src/sys/netinet/udp_usrreq.c
FreeBSD 7.1-PRERELEASE #18: Sat Sep 20 23:38:22 BRT 2008
On Sat, 20 Sep 2008, Simon L. Nielsen wrote:
- The more branches are supported, the more versions of both third
party code and FreeBSD code need to be supported and the more likely
it is that the software differs meaning that we need to adopt the
fix to the branch. The real painful case for
On Sat, 20 Sep 2008, Vlad GALU wrote:
Will the zero-copy bpf(4) changes be merged to the stable branch before
the release?
Dear Vlad:
Unfortunately, no. The code seems stable in 8-CURRENT, but I don't feel it's
had enough actual testing exposure to go into 7.x yet. Also, the libpcap
cha
in my experience, in usual kernel && userland upgrading is good,
however, everytime port upgrading have problem, whenever new -REL is
released ;; i usually do port upgrading by portupgrade(1).
at once(when 6.2-REL was released) i did upgrading port by
portupgrade(1) but i met failures on the upgra
On Sat, 20 Sep 2008, netgeek wrote:
Don't get me wrong: I would love to see us support all releases for 24
months (or even more) after they ship. I think our users would appreciate
that also.
Perhaps there is a middle ground here? What about a statement that each
major branch (6.x, 7.x) w
42 matches
Mail list logo
