* Bruce M Simpson [Fr, 21 Nov 2003 at 20:36 GMT]:
> On Wed, Nov 19, 2003 at 05:32:37PM -0800, Sean Chittenden wrote:
>> I don't know if Lucent cards are supported or not. How old is your
>> kernel, btw? You should update to -CURRENT as there have been many
>> wlan fixes since 5.1-RELEASE. -sc
>
* Dimitry Andric [Di, 21 Okt 2003 at 20:19 GMT]:
>
> Today I had a -CURRENT machine panic on me with a page fault, and
> something happened that I have seen before: the machine refused to
> come up afterwards. Closer inspection revealed that the MBR on the
> boot disk was totally zapped, filled wi
* Pawel Jakub Dawidek [Di, 14 Okt 2003 at 11:45 GMT]:
>
>
> I'm not sure if this was reported already.
I think so,
http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008743.html
regards
tilman
pgp0.pgp
Description: PGP signature
Hi,
Updated my -CURRENT yesterday and got the following panic:
[...]
atapci0: port 0xb800-0xb80f at
device 15.0 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
fdc0: port
0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes th
Hi,
Today I did something stupid. I umount'ed a filesystem of my NFS Server,
while an NFS client was writing to it.
My NFS Server is:
polly# uname -a
FreeBSD polly.arved.de 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Sat Aug 16
10:11:52 CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/source/CURRENT/sys/POLL
* Tilman Linneweh [Fr, 15 Aug 2003 at 16:17 GMT]:
>
> My CURRENT is already a bit old:
>
> # uname -a
> FreeBSD polly.arved.de 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Sun Jul 20
> 01:00:14 CEST 2003
> [EMAIL PROTECTED]:/usr/obj/usr/src/CURRENT/sys/POLLY i386
I updated
Hi list,
My CURRENT is already a bit old:
# uname -a
FreeBSD polly.arved.de 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Sun Jul 20
01:00:14 CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/CURRENT/sys/POLLY i386
But at least the first problem looks like it hasn't been fixed yet:
This happend while the
* Kris Kennaway [Di, 24 Jun 2003 at 03:13 GMT]:
>
>> > > I installed freebsd-games, and it has most of the games I remember, b=
> ut n=3D
>> > ot
>> > > rogue.
>> >=20
>> > Well, hrumph, it's supposed to be in that port. Mark, it looks like
>> > rogue wasn't added for some reason.
>>=20
>> Oops.
In arved.freebsd.current, you wrote:
> I updated my 5.0 system built in late January to RELENG_5_0 on Sunday
> and the Ethernet was not working. I tried again last night with no
> change in behavior.
>
> The system is an AMD K6-2 on an ASUS P5A mobo. I have a 3Com 3c905B
> Ethernet which had been
* "Petr Holub" <[EMAIL PROTECTED]> [Sun, 1 Dec 2002 16:38:26 +0100]:
> > Have you tried the update submitted in PR ports 43484? I didn't tested it
> > on CURRENT yet (due to lack of Kerberos on my CURRENT box).
>
> The seems to just to upgrade to 0.36.9. I tried to compile both 0.35.9
> and 0.36.
In arved.freebsd.current, you wrote:
> Hi all,
>
> I tried to build arla on 5.0-DP2 and got messages following my
> signature. It seems that some structures changed since 4-STABLE.
> I'm building it on my own using patches from port tree. This
> procedure works on 4.x flawlessly.
>
Have you tried
Hi,
I can reproducable panic todays CURRENT by running ifconfig xl0 up
(My rl0 NIC works fine). The xl0 NIC works on STABLE.
Any help/ideas appreciated.
regards
tilman
polly# ifconfig xl0 up
panic: invalid ife->ifm_data (0x6000) in mii_phy_setmedia
Debugger("panic")
Stopped at Debugger+0x
In freebsd.current, you wrote:
>
> Just got everything up, made sure that it knew how to mount my file
> systems, watched it fsck those same file systems ... but as soon as it
> started to install, it reported out of space errors ...
>
> On ALT-F2, it looks like its trying to write to:
>
> ./usr
> I have a problem with my ASUS P5A-B motherboard, where the timer
> runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago.
>
> I encountered this problem before, and found a fix which worke;:
>
>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=145760+0+archive/2002/freebsd-current/200209
14 matches
Mail list logo
