Many Hardware Problems with AMD 64-bit 4.2 - BSD

This is a discussion on Many Hardware Problems with AMD 64-bit 4.2 - BSD ; Keyboard, cdrom, usb. All worked with 4.1; all have problems now....

+ Reply to Thread
Results 1 to 7 of 7

Thread: Many Hardware Problems with AMD 64-bit 4.2

  1. Many Hardware Problems with AMD 64-bit 4.2

    Keyboard, cdrom, usb. All worked with 4.1; all have problems now.

  2. Re: Many Hardware Problems with AMD 64-bit 4.2

    D wrote:
    > Keyboard, cdrom, usb. All worked with 4.1; all have problems now.


    Keyboard for root console: do not reflect current state of keyboard.
    Ie they don't go on/off when corresponding keys are pressed.
    Keyboards for consoles 2-4 do work properly.

    CDROM drive will not open when OpenBSD is running.

    USB drives no longer work.

    All this after an install from cdrom.

    dmesg:
    ----------------

    OpenBSD 4.2 (GENERIC) #1179: Tue Aug 28 10:37:50 MDT 2007
    deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
    real mem = 536276992 (511MB)
    avail mem = 509337600 (485MB)
    mainbus0 at root
    bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfd470 (58 entries)
    bios0: vendor American Megatrends Inc. version "080013 " date 04/24/2006
    bios0: MSI MS-7260
    acpi at mainbus0 not configured
    cpu0 at mainbus0: (uniprocessor)
    cpu0: AMD Athlon(tm) 64 Processor 3500+, 2211.61 MHz
    cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,P GE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE 3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW
    cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache
    cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
    cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
    pci0 at mainbus0 bus 0: configuration mode 1
    "NVIDIA MCP55 Memory" rev 0xa1 at pci0 dev 0 function 0 not configured
    pcib0 at pci0 dev 1 function 0 "NVIDIA MCP55 ISA" rev 0xa2
    nviic0 at pci0 dev 1 function 1 "NVIDIA MCP55 SMBus" rev 0xa2
    iic0 at nviic0
    iic1 at nviic0
    iic1: addr 0x2f 00=c0 01=0f 02=00 03=01 04=07 05=00 06=18 07=00 08=00 14=14 15=62 16=02 17=05
    "NVIDIA MCP55 Memory" rev 0xa2 at pci0 dev 1 function 2 not configured
    ohci0 at pci0 dev 2 function 0 "NVIDIA MCP55 USB" rev 0xa1: irq 15, version 1.0, legacy support
    ehci0 at pci0 dev 2 function 1 "NVIDIA MCP55 USB" rev 0xa2: irq 10
    usb0 at ehci0: USB revision 2.0
    uhub0 at usb0: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1
    pciide0 at pci0 dev 4 function 0 "NVIDIA MCP55 IDE" rev 0xa1: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility
    atapiscsi0 at pciide0 channel 0 drive 0
    scsibus0 at atapiscsi0: 2 targets
    cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable
    cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
    pciide0: channel 1 ignored (disabled)
    pciide1 at pci0 dev 5 function 0 "NVIDIA MCP55 SATA" rev 0xa2: DMA
    pciide1: using irq 11 for native-PCI interrupt
    wd0 at pciide1 channel 0 drive 0:
    wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
    wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
    pciide2 at pci0 dev 5 function 1 "NVIDIA MCP55 SATA" rev 0xa2: DMA
    pciide2: using irq 5 for native-PCI interrupt
    ppb0 at pci0 dev 6 function 0 "NVIDIA MCP55 PCI-PCI" rev 0xa2
    pci1 at ppb0 bus 1
    bktr0 at pci1 dev 0 function 0 "Brooktree BT878" rev 0x11: irq 11
    bktr0: Hauppauge WinCast/TV, tuner.
    "Brooktree BT878 Audio" rev 0x11 at pci1 dev 0 function 1 not configured
    "Brooktree BT878" rev 0x11 at pci1 dev 1 function 0 not configured
    "Brooktree BT878 Audio" rev 0x11 at pci1 dev 1 function 1 not configured
    azalia0 at pci0 dev 6 function 1 "NVIDIA MCP55 HD Audio" rev 0xa2: irq 15
    azalia0: host: High Definition Audio rev. 1.0
    azalia0: codec: Realtek ALC883 (rev. 0.2), HDA version 1.0
    audio0 at azalia0
    nfe0 at pci0 dev 8 function 0 "NVIDIA MCP55 LAN" rev 0xa2: irq 10, address 00:16:17:47:3f:9e
    ukphy0 at nfe0 phy 1: Generic IEEE 802.3u media interface, rev. 0: OUI 0x0001c1, model 0x0002
    ppb1 at pci0 dev 11 function 0 "NVIDIA MCP55 PCIE" rev 0xa2
    pci2 at ppb1 bus 2
    ppb2 at pci0 dev 12 function 0 "NVIDIA MCP55 PCIE" rev 0xa2
    pci3 at ppb2 bus 3
    ppb3 at pci0 dev 13 function 0 "NVIDIA MCP55 PCIE" rev 0xa2
    pci4 at ppb3 bus 4
    ppb4 at pci0 dev 14 function 0 "NVIDIA MCP55 PCIE" rev 0xa2
    pci5 at ppb4 bus 5
    ppb5 at pci0 dev 15 function 0 "NVIDIA MCP55 PCIE" rev 0xa2
    pci6 at ppb5 bus 6
    vga1 at pci6 dev 0 function 0 "ATI Radeon X300" rev 0x00
    wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
    wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
    "ATI Radeon X300 Sec" rev 0x00 at pci6 dev 0 function 1 not configured
    pchb0 at pci0 dev 24 function 0 "AMD AMD64 HyperTransport" rev 0x00
    pchb1 at pci0 dev 24 function 1 "AMD AMD64 Address Map" rev 0x00
    pchb2 at pci0 dev 24 function 2 "AMD AMD64 DRAM Cfg" rev 0x00
    pchb3 at pci0 dev 24 function 3 "AMD AMD64 Misc Cfg" rev 0x00
    isa0 at pcib0
    isadma0 at isa0
    com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
    com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 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
    pmsi0 at pckbc0 (aux slot)
    pckbc0: using irq 12 for aux slot
    wsmouse0 at pmsi0 mux 0
    pcppi0 at isa0 port 0x61
    midi0 at pcppi0:
    spkr0 at pcppi0
    lpt0 at isa0 port 0x378/4 irq 7
    usb1 at ohci0: USB revision 1.0
    uhub1 at usb1: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1
    umass0 at uhub0 port 10 configuration 1 interface 0
    umass0: Generic Mass Storage Device, rev 2.00/1.00, addr 2
    umass0: using SCSI over Bulk-Only
    scsibus1 at umass0: 2 targets
    sd0 at scsibus1 targ 1 lun 0: SCSI0 0/direct removable
    sd0: drive offline
    sd1 at scsibus1 targ 1 lun 1: SCSI0 0/direct removable
    sd1: drive offline
    sd2 at scsibus1 targ 1 lun 2: SCSI0 0/direct removable
    sd2: drive offline
    sd3 at scsibus1 targ 1 lun 3: SCSI0 0/direct removable
    sd3: drive offline
    uhub1: device problem, disabling port 8
    dkcsum: wd0 matches BIOS drive 0x80
    root on wd0a swap on wd0b dump on wd0b
    sd0(umass0:1:0): Check Condition (error 0x70) on opcode 0x0
    SENSE KEY: Not Ready
    COMMAND INFO: 0xaa5540
    ASC/ASCQ: Medium Not Present
    sd2(umass0:1:2): Check Condition (error 0x70) on opcode 0x0
    SENSE KEY: Not Ready
    COMMAND INFO: 0xaa5540
    ASC/ASCQ: Medium Not Present
    sd0(umass0:1:0): Check Condition (error 0x70) on opcode 0x0
    SENSE KEY: Not Ready
    COMMAND INFO: 0xaa5540
    ASC/ASCQ: Medium Not Present
    sd1(umass0:1:1): Check Condition (error 0x70) on opcode 0x0
    SENSE KEY: Not Ready
    COMMAND INFO: 0xaa5540
    ASC/ASCQ: Medium Not Present
    sd2(umass0:1:2): Check Condition (error 0x70) on opcode 0x0
    SENSE KEY: Not Ready
    COMMAND INFO: 0xaa5540
    ASC/ASCQ: Medium Not Present
    sd3(umass0:1:3): Check Condition (error 0x70) on opcode 0x0
    SENSE KEY: Not Ready
    COMMAND INFO: 0xaa5540
    ASC/ASCQ: Medium Not Present

  3. Re: Many Hardware Problems with AMD 64-bit 4.2

    D wrote:
    > D wrote:
    >> Keyboard, cdrom, usb. All worked with 4.1; all have problems now.

    >
    > Keyboard for root console: do not reflect current state of keyboard.
    > Ie they don't go on/off when corresponding keys are pressed.
    > Keyboards for consoles 2-4 do work properly.
    >
    > CDROM drive will not open when OpenBSD is running.
    >
    > USB drives no longer work.
    >
    > All this after an install from cdrom.


    See latest details of these and other problems at
    http://dfeustel.home.mindspring.com

  4. Re: Many Hardware Problems with AMD 64-bit 4.2

    I know how to killfile "daf@puf.localhost.comcast.net". There is no
    point reading his frequent inane posts about self-inflicted computer
    injuries.

    But if I don't see his original posts, then I don't know which threads
    he has started, so I still have to wade through the replies.

    Does anyone know how to teach trn to automatically kill any thread
    that was started by Dave Feustel? Is there a complicated logical
    expression that I can use in my killfile?

    Signed: Happy OpenBSD user, who occasionally has problems with it.

    --
    Ralph Becker-Szendy _firstname_@lr_dot_los-gatos_dot_ca_dot_us
    735 Sunset Ridge Road; Los Gatos, CA 95033

  5. Re: Many Hardware Problems with AMD 64-bit 4.2

    _firstname_@lr_dot_los-gatos_dot_ca_dot_us wrote:
    > I know how to killfile "daf@puf.localhost.comcast.net". There is no
    > point reading his frequent inane posts about self-inflicted computer
    > injuries.
    >
    > But if I don't see his original posts, then I don't know which threads
    > he has started, so I still have to wade through the replies.
    >
    > Does anyone know how to teach trn to automatically kill any thread
    > that was started by Dave Feustel? Is there a complicated logical
    > expression that I can use in my killfile?
    >
    > Signed: Happy OpenBSD user, who occasionally has problems with it.


    It might be simpler to just kill yourself.

  6. Re: Many Hardware Problems with AMD 64-bit 4.2

    On Tue, 30 Oct 2007 14:11:59 -0500, D wrote:

    > _firstname_@lr_dot_los-gatos_dot_ca_dot_us wrote:
    >> I know how to killfile "daf@puf.localhost.comcast.net". There is no
    >> point reading his frequent inane posts about self-inflicted computer
    >> injuries.
    >>
    >> But if I don't see his original posts, then I don't know which threads
    >> he has started, so I still have to wade through the replies.
    >>
    >> Does anyone know how to teach trn to automatically kill any thread
    >> that was started by Dave Feustel? Is there a complicated logical
    >> expression that I can use in my killfile?
    >>
    >> Signed: Happy OpenBSD user, who occasionally has problems with it.

    >
    > It might be simpler to just kill yourself.


    Gosh, it feels exactly like alt.os.linux.* in here right now.

  7. Re: Many Hardware Problems with AMD 64-bit 4.2

    Mark South wrote:
    > On Tue, 30 Oct 2007 14:11:59 -0500, D wrote:
    >
    >> _firstname_@lr_dot_los-gatos_dot_ca_dot_us wrote:
    >>> I know how to killfile "daf@puf.localhost.comcast.net". There is no
    >>> point reading his frequent inane posts about self-inflicted computer
    >>> injuries.
    >>>
    >>> But if I don't see his original posts, then I don't know which threads
    >>> he has started, so I still have to wade through the replies.
    >>>
    >>> Does anyone know how to teach trn to automatically kill any thread
    >>> that was started by Dave Feustel? Is there a complicated logical
    >>> expression that I can use in my killfile?
    >>>
    >>> Signed: Happy OpenBSD user, who occasionally has problems with it.

    >>
    >> It might be simpler to just kill yourself.

    >
    > Gosh, it feels exactly like alt.os.linux.* in here right now.


    I have changed my handle to make it easier for _firstname_ to find and
    kill my posts.

+ Reply to Thread