Re: openbsd 4.0 installed, need to add network interface after install
> I am doing this in a 1U box, so there is a pci 1u > riser card. Could it be the riser is bad? Maybe, you could remove the bracket from a PCI card and try it with the case lid off and no riser for a test (and other slots if you have any).. Have a look for leaky capacitors while you're there, if you haven't already seen your fair share, look at http://badcaps.net/ident/
Re: openbsd 4.0 installed, need to add network interface after install
On 6/29/07, Brian Candler <[EMAIL PROTECTED]> wrote: Given that your on-board LAN isn't working either, maybe the motherboard has a serious fault. But you might not be able to return it until you can prove that *Windows* can't find any network cards either :-) that's simple, create a screen session with (multiple) windows in it and show them ifconfig -A in each of those. :) -- almir
Re: openbsd 4.0 installed, need to add network interface after install
On Fri, Jun 29, 2007 at 12:40:56PM -0700, John Mendenhall wrote: > I booted an ultimate boot disk, with several small linux distros > on them. None of them found the card. I'd personally go with a full-sized Linux distro, as it's more likely to have a complete driver set, but it does seem more like a hardware issue now. > I reseated the card. No go. > I tried another card I had, same model. Nothing. > I am doing this in a 1U box, so there is a pci 1u > riser card. Could it be the riser is bad? Or, > could the pci slot itself be bad? Yes it's possible. (But then again, I think you said the motherboard had an on-board NIC too, and that wasn't working either?) > What is the best way to test the pci slot? If you remove the motherboard from its case, can you insert a PCI card directly, not using the riser? If you have a PCI card which definitely works in another unit (say something which appears as fxp0 in another box), so much the better. Given that your on-board LAN isn't working either, maybe the motherboard has a serious fault. But you might not be able to return it until you can prove that *Windows* can't find any network cards either :-) Regards, Brian.
Re: openbsd 4.0 installed, need to add network interface after install
On Fri, Jun 29, 2007 at 03:16:36PM +0200, St?phane Chausson wrote: > Brian Candler wrote, On 29/06/07 14:43: > >Also, under Linux, "lspci -v" gives useful info about the PCI cards you > >have > >installed. In theory, you should be able to do this with OpenBSD too: > >http://mj.ucw.cz/pciutils.shtml > > > >However it doesn't work for me: > > > ># pkg_add > >ftp://ftp.openbsd.org/pub/OpenBSD/4.0/packages/i386/pciutils-2.2.1.tgz > >pciutils-2.2.1: complete > ># lspci -v > >lspci: obsd_init: /dev/pci open failed > > > > From the pkg_info of pciutils, you have to set machdep.allowaperture=2 > via sysctl(8) > > I set it to 0 and got the same error as the one you show Thank you, that fixed it. (However I couldn't modify this value using sysctl while the system was running; I had to put it in /etc/sysctl.conf and reboot) # lspci -v ... 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at b800 Memory at fe5ffc00 (32-bit, non-prefetchable) Capabilities: [50] Power Management version 2 01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02) Subsystem: GVC/BCM Advanced Research Unknown device 2181 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at fe5ee000 (32-bit, non-prefetchable) I/O ports at bc00 Capabilities: [dc] Power Management version 2 (Those are rl0 and fxp0 respectively) So maybe the OP can do this too and see if any network cards are reported. Regards, Brian.
Re: openbsd 4.0 installed, need to add network interface after install
Brian, > > 1- Check the hardware compatability list to make sure the > > lan card is supported. > > 2- Take a look and make sure the lan card is seated in it's > > slot properly. I have had this happen a few times with > > smaller cards not seating all the way (it's probably because > > of my fat paws). > > 3. Temporarily boot from another operating system's "live CD", e.g. >FreeBSD 6.2 disc 1 (select "fixit" mode to get a shell) > >For a Linux view try Ubuntu 6.06.1, or Fedora 7 for a more >bleeding-edge kernel. These two require you to wait for a graphical >environment to start though. > > These will show you if another OS recognises the card(s) you have. I booted an ultimate boot disk, with several small linux distros on them. None of them found the card. I reseated the card. No go. I tried another card I had, same model. Nothing. I am doing this in a 1U box, so there is a pci 1u riser card. Could it be the riser is bad? Or, could the pci slot itself be bad? What is the best way to test the pci slot? Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 4.0 installed, need to add network interface after install
Stuart, > I'm far from a guru, but looking at your dmesg I don't see > a lan card there at all. Here are the first few steps: > > 1- Check the hardware compatability list to make sure the > lan card is supported. > 2- Take a look and make sure the lan card is seated in it's > slot properly. I have had this happen a few times with > smaller cards not seating all the way (it's probably because > of my fat paws). The linksys lne100tx card is listed twice, once as 4.x, and another time with no version. My lne100tx cards are both v5.1. I have tried both. Neither work. No lights on back. Nothing. Is it possible for the pci slot to be bad? > btw, for an add on card, you probably won't see anything in the > systems bios, that is unless bios systems have > gotten much more functional than they were last time I looked. Understood. Thanks so much for your input. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 4.0 installed, need to add network interface after install
> 1- Check the hardware compatability list to make sure the > lan card is supported. > 2- Take a look and make sure the lan card is seated in it's > slot properly. I have had this happen a few times with > smaller cards not seating all the way (it's probably because > of my fat paws). 3. Temporarily boot from another operating system's "live CD", e.g. FreeBSD 6.2 disc 1 (select "fixit" mode to get a shell) For a Linux view try Ubuntu 6.06.1, or Fedora 7 for a more bleeding-edge kernel. These two require you to wait for a graphical environment to start though. These will show you if another OS recognises the card(s) you have. Also, under Linux, "lspci -v" gives useful info about the PCI cards you have installed. In theory, you should be able to do this with OpenBSD too: http://mj.ucw.cz/pciutils.shtml However it doesn't work for me: # pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.0/packages/i386/pciutils-2.2.1.tgz pciutils-2.2.1: complete # lspci -v lspci: obsd_init: /dev/pci open failed ktrace and kdump just show: ... 4341 lspciCALL open(0x3c002b8b,0x2,0) 4341 lspciNAMI "/dev/pci" 4341 lspciRET open -1 errno 1 Operation not permitted ... Regards, Brian.
Re: openbsd 4.0 installed, need to add network interface after install
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
> John Mendenhall
> Sent: Thursday, June 28, 2007 03:37 PM
> To: misc@openbsd.org
> Subject: openbsd 4.0 installed, need to add network interface after
> install
>
>
> openbsd gurus,
>
> As the saga continues...
> I have a newly built server with openbsd 4.0.
> During installation, it did not find the onboard
> lan interface, which I did not realize until after
> the installation had completed.
>
> I made sure the bios was set properly. There
> was no LAN option in the BIOS.
>
> I assumed the onboard lan interface was bad.
> This has happened before so I added a linksys
> lan card in the system.
>
> I rebooted. I checked the BIOS for any LAN options.
> Nothing. I booted into openbsd. No interfaces
> created.
>
> How do I get the system to discover the network
> interface?
>
> I have been searching the net for anything like
> this and have not found anything that has worked.
>
> Do I need to reinstall the system?
> Or, is there some tool I can use to rediscover the
> network interface so it gets setup properly?
>
> Thanks in advance for any pointers you can provide.
>
> JohnM
>
> Here is my current dmesg:
> --
> OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD Athlon(tm) ("AuthenticAMD" 686-class, 256KB L2 cache) 1.01 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,
> PSE36,MMX,FXSR,SSE
> real mem = 527986688 (515612K)
> avail mem = 473665536 (462564K)
> using 4256 buffers containing 26501120 bytes (25880K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(08) BIOS, date 12/24/01, BIOS32 rev. 0
> @ 0xfb420, SMBIOS rev. 2.2 @ 0xf0800 (31
> entries)
> bios0: VIA Technologies, Inc. VT8361
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> apm0: flags 70102 dobusy 1 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf/0xdef4
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde70/128 (6 entries)
> pcibios0: PCI Exclusive IRQs: 10 11
> pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C596A ISA" rev 0x00)
> pcibios0: PCI bus #1 is the last bus
> bios0: ROM list: 0xc/0xc000 0xcc000/0x4000!
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "VIA VT8361 PCI" rev 0x00
> ppb0 at pci0 dev 1 function 0 "VIA VT8361 AGP" rev 0x00
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "Trident CyberBlade i1" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
> pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06:
> ATA100, channel 0 configured to compatibility
> , channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> wd1 at pciide0 channel 1 drive 0:
> wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
> atapiscsi0 at pciide0 channel 1 drive 1
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: SCSI0
> 5/cdrom removable
> wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x1a: irq 10
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> uhci1 at pci0 dev 7 function 3 "VIA VT83C572 USB" rev 0x1a: irq 10
> usb1 at uhci1: USB revision 1.0
> uhub1 at usb1
> uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
> uhub1: 2 ports with 2 removable, self powered
> viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0:
> spkr0 at pcppi0
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> pccom0: console
> biomask ffed netmask ffed ttymask ffef
> pctr: user-level cycle counter enabled
> mtrr: Pentium Pro MTRR support
> dkcsum: wd0 matches BIOS drive 0x80
> dkcsum: wd1 matches BIOS drive 0x81
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
> --
>
> --
> john mendenhall
> [EMAIL PROTECTED]
> surf utopia
> internet services
>
John,
I'm far from a guru, but looking at your dmesg I don't see
a lan card there at all. Here are the first few steps:
1- Check the hardware compatability list to make sure the
lan card is supported.
2- Take a look and make sure the lan card is seated in it's
slot properly. I have had this happen a few times with
smaller cards not seating all the way (it
