Re: Intel D201GLY2 install failure, OpenBSD 4.4
Thanks to LEVAI Daniel for providing his dmesg. To add mere confirmation, I too was able to boot 4.4 release with NIC interface active/recognized after 'boot -c' + 'disable acpi', however I was unable to muster the skill to accomplish the ftp transfer. Is Daniel's dmesg sufficient for debug, or would a capture of a default-config dmesg (with all its error messages) be beneficial? If the latter, I will endeavor to connect a floppy drive... Jaime --- On Fri, 11/7/08, Ted Unangst [EMAIL PROTECTED] wrote: From: Ted Unangst [EMAIL PROTECTED] Subject: Re: Intel D201GLY2 install failure, OpenBSD 4.4 To: [EMAIL PROTECTED] Cc: misc@openbsd.org Date: Friday, November 7, 2008, 9:24 AM On Fri, Nov 7, 2008 at 8:54 AM, Jamie Cuesta [EMAIL PROTECTED] wrote: It seems that in order to use the ftp option, I need a functioning network interface(?). However when I boot using the install CD and choose (s)hell, here's what I see: # ifconfig lo0: flags=8008LOOPBACK,MULTICAST mtu 33204 groups: lo # Note that one of the boot messages in my first post seemed to indicate that the on-Mobo NIC was among the devices affected by a bad interrupt problem: sis0 at pci0 dev 4 function 0 SiS 900 10/100BaseTX rev 0x91pci_intr_map: bad interrupt line 19 : couldn't map interrupt Ok, you are having serious interrupt issues. The only thing I can think of to try is disabling acpi (via boot -c), but that's a long shot.
Re: Intel D201GLY2 install failure, OpenBSD 4.4
From: Ted Unangst [EMAIL PROTECTED] Subject: Re: Intel D201GLY2 install failure, OpenBSD 4.4 To: [EMAIL PROTECTED] Cc: misc@openbsd.org Date: Thursday, November 6, 2008, 1:24 PM On Thu, Nov 6, 2008 at 11:49 AM, Jamie Cuesta [EMAIL PROTECTED] wrote: I was hoping to include a dmesg via serial port capture (my box does not include a floppy), but Use ftp. First: I'm a noob, so some of what follows may be utterly basic and ignorant. It seems that in order to use the ftp option, I need a functioning network interface(?). However when I boot using the install CD and choose (s)hell, here's what I see: # ifconfig lo0: flags=8008LOOPBACK,MULTICAST mtu 33204 groups: lo # Note that one of the boot messages in my first post seemed to indicate that the on-Mobo NIC was among the devices affected by a bad interrupt problem: sis0 at pci0 dev 4 function 0 SiS 900 10/100BaseTX rev 0x91pci_intr_map: bad interrupt line 19 : couldn't map interrupt Is there any way around this (involving only the shell available to me now)? If not, I suppose I'll see if I can dig a floppy drive out of my bonepile and pray that _it_ works. Thanks, Jaime
Intel D201GLY2 install failure, OpenBSD 4.4
I'm booting from CD as prelude to install, and during CD boot see (NOTE this is manually transcribed from the screen): : couldn't map interrupt sis0 at pci0 dev 4 function 0 SiS 900 10/100BaseTX rev 0x91pci_intr_map: bad interrupt line 19 : couldn't map interrupt pciide1 at pci0 dev 5 function 0 SiS 181 SATA rev 0x01: DMA pci_intr_map: bad interrupt line 17 pciide1: couldn't map native-PCI interrupt pci_intr_map: bad interrupt line 17 pciide1: couldn't map native-PCI interrupt ppb1 at pci0 dev 31 function 0 SiS PCI-PCI rev 0x00 pci2 at ppb1 bus 2 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x2f8/8 irq 4: ns 16550a, 16 byte fifo 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 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 biomask ffed netmask ffed ttymask rd0: fixed, 3800 blocks softraid at root root on rd0a swap on rd0b dump on rd0b erase ^?, werase ^W, kill ^U, intr ^C, status ^T (I)nstall, (U)pgrade or (S)hell? I choose install, accept defaults for terminal type, answer 'y' to Proceed with install? [no] and get: No disks found. # This system has a IDE CD-RW drive, and two SATA HDD's. After failing OpenBSD 4.4 install last week, I installed Debian stable on this system w/no problems. But I'd rather use OpenBSD so reporting this problem in hopes it can be fixed (mobo is a nice low-cost fanless mini-ITX, so could appeal to many). My web searches show this problem being reported occasionally in the past but none I saw no reports for this mobo with 4.4 release. I was hoping to include a dmesg via serial port capture (my box does not include a floppy), but boot set tty com0 switching console to com0 com0 console not present Web searches suggested I could mess with the BIOS to get around this problem, but the only BIOS setting for the serial port is enable/disable: I switched to disable mode with no change in results. FWIW, Jaime
