On Fri, 27 Jun 2008 11:55:45 +0200, Ronald Klop
[EMAIL PROTECTED] wrote:
On Thu, 26 Jun 2008 18:01:07 +0200, Gavin Atkinson
[EMAIL PROTECTED] wrote:
On Thu, 2008-06-26 at 16:09 +0200, Ronald Klop wrote:
Hello,
At my work I see a panic if I do this.
Leaf my computer on screensaver (don't
On Sun, Jul 06, 2008 at 10:45:28PM +0200, Krzysztof J??druczyk wrote:
Pyun YongHyeon pisze:
Would you try the patch at the following URL?
http://people.freebsd.org/~yongari/msk/msk.88E8040.patch5
The diff generated against HEAD and it could be cleanly applied to
7-stable. 7-stable
Hi!
Today I've updated my 7.0-STABLE system using source upgrade path.
loader(8) boots it just fine but it's impossible to issue commands
using its command prompt mode (N.B.: beastie_disable=YES
and autoboot_delay=2 are in my /boot/loader.conf).
At boot time, I hit Space button to reach its
On Sun, 2008-07-06 at 13:15 +0200, Jilles Tjoelker wrote:
On Sun, Jun 29, 2008 at 04:16:25PM -0400, Alexandre Sunny Kovalenko wrote:
I honestly don't know whether it should or should not do it, and if it
should not, what errno should be set to. Program below gives following
output on
Pyun YongHyeon wrote:
Since the patch had lots of code not related with 88E8062 dual port
controller, would you try attached patch again? I think the attached
patch is minimal one that makes 88E8062 work.
The patch also try to enable MSI for dual port controllers. At the
time of writing
I have a brand new Supermicro server that seems to be having issues with the em
devices. I installed FreeBSD 7.0-Release from CDs and everything was working
fine and then decided to cvsup to 7 stable and then I lost my em devices and
thus networking. Reboots/power cycling didn't change it - no
Date: Mon, 7 Jul 2008 18:21:47 +0800
From: Eugene Grosbein [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Hi!
Today I've updated my 7.0-STABLE system using source upgrade path.
loader(8) boots it just fine but it's impossible to issue commands
using its command prompt mode (N.B.:
Date: Mon, 7 Jul 2008 18:21:47 +0800
From: Eugene Grosbein [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Hi!
Today I've updated my 7.0-STABLE system using source upgrade path.
loader(8) boots it just fine but it's impossible to issue commands
using its command prompt mode (N.B.:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Alan,
alan bryan wrote:
| I have a brand new Supermicro server that seems to be having issues
with the em devices. I installed FreeBSD 7.0-Release from CDs and
everything was working fine and then decided to cvsup to 7 stable and
then I lost my
I got Intel D945GCLF and it has Realtek 8102EL chip.
But it is not found by kernel. dmesg does not display as 're' or 'rl'.
How to find hwrev (revision code) to add if_rlreg.h and if_re.c ?
I'm using 6.3-R and added this change, but revision is not displayed.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NAGATA Shinya wrote:
| I got Intel D945GCLF and it has Realtek 8102EL chip.
| But it is not found by kernel. dmesg does not display as 're' or 'rl'.
|
| How to find hwrev (revision code) to add if_rlreg.h and if_re.c ?
| I'm using 6.3-R and added
Could you please try 'boot -v' and see if there is some error messages?
're0' is displayed. But it seems like kernel couldn't find a driver.
| re0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x2000
| pci1: network, ethernet at device 0.0 (no driver attached)
--
NAGATA Shinya
Consoles:
Should igb be in the GENERIC config file?
pwd
/usr/src/sys/amd64/conf
cat GENERIC | grep igb
I did a kldload if_igb and that seemed to work and I now have a igb0 device.
I get an error though on the other (unused igb1) network port:
igb0: Intel(R) PRO/1000 Network Connection version -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
alan bryan wrote:
| Should igb be in the GENERIC config file?
|
| pwd
| /usr/src/sys/amd64/conf
| cat GENERIC | grep igb
Ah... I really thought it is supposed to be there. Jack, I think we
will want this in GENERIC kernel, do you have objections?
On Mon, Jul 07, 2008 at 03:47:28PM -0700, alan bryan wrote:
Should igb be in the GENERIC config file?
pwd
/usr/src/sys/amd64/conf
cat GENERIC | grep igb
I did a kldload if_igb and that seemed to work and I now have a igb0
device.
I get an error though on the other
On Tue, Jul 08, 2008 at 07:35:30AM +0900, NAGATA Shinya wrote:
Could you please try 'boot -v' and see if there is some error messages?
're0' is displayed. But it seems like kernel couldn't find a driver.
| re0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x2000
| pci1: network,
I have same motherboard and I tried re patch as follows.
The result is still failed.
http://people.freebsd.org/~yongari/re/re.HEAD.20080624
re0: RealTek 8101E PCIe 10/100baseTX port 0x2000-0x20ff mem 0x4820-0x48200
fff,0x4800-0x4800 irq 16 at device 0.0 on pci1
re0: Chip rev.
On Tue, Jul 08, 2008 at 10:14:15AM +0900, Tadashi Takahashi wrote:
I have same motherboard and I tried re patch as follows.
The result is still failed.
http://people.freebsd.org/~yongari/re/re.HEAD.20080624
re0: RealTek 8101E PCIe 10/100baseTX port 0x2000-0x20ff mem
Yes, I guess the time has arrived to add igb into GENERIC, I
would add into your kernel config now, I will add into the tree
at my next opportunity.
As for that failure on igb1, try building in the kernel and see
if that still happens, that one I have not seen.
Cheers,
Jack
On Mon, Jul 7,
19 matches
Mail list logo
