Re: 3.0.3 on Durango: some problems

Bas Kelderman (damas@dds.nl)
Thu, 14 Nov 1996 15:44:13 +0100

Hmm, I get the same problems with my AXPpci33, didn't get Linux to boot so
couldn't check the devices that far, but MILO hasthe same oddities here.

Bas Kelderman
b.kelderman@dyme.nl

----------
> From: geerten kuiper <geerten@bart.nl>
> To: axp-list@redhat.com
> Subject: 3.0.3 on Durango: some problems
> Date: donderdag 14 november 1996 11:50
>
> All,
>
> Yesterday I finally put together my new hardware, and installed RedHat
3.0.3
> (using a PC164 kernel from 4.0, and apropriately new MILO/LinLoad: thanks
to
> Wolfgang Dreyer). Only problem during install was, I had to do mke2fs
from
> the second VC by hand.
>
> So now I've got it running, but some problems/oddities are remaining.
>
> - the firmware clock had not updated the date this morning. Time seems to
be
> OK though.
>
> - MILO complains about not detecting the NVRAM. (I do not know if this is
a
> problem)
>
> - Mouse: Firmware sees a serial mouse on COM2, which is correct. Kernel
> claims it sees a PS/2 mouse, which is not correct. In the XF86Config I
set
> up the serial mouse, but it doesn't work: when I move it the pointer
stays
> in place for a while (many seconds, maybe a minute) then suddenly jumps
to a
> new position. I have tried replacing the mouse, but to no avail.
>
> - Ethernet: I have an ACCTON NE2000-clone in one of the ISA slots, and
the
> kernel should see it as "eth0: NE2000 found at 0x300, using IRQ 5." It
does,
> but only occasionally (one time out of five or worse) The other times it
> says "NE*000 ethercard probe at 0x300: failed to detect IRQ line."
> I have two of those cards, both work fine in the Pentium, both fail in
the
> Alpha, so I guess there's nothing wrong with the card itself.
>
> - There are some other things that work sometimes, but more often do not:
> Ctrl-Alt-Del or "shutdown -r now" may cycle through MILO and reboot, but
> usually hangs.
> "date" may show the right date, but usually does not. (even after setting
> CLOCKMODE="ARC") (it is consistent from boot to shutdown.)
>
> - Doing "time" will get the Elapsed time wrong. (I believe this one has
been
> on the list before.)
>
> As some of these problems seem to be related to interrupts, I checked
> /proc/interrupts.
> It shows
> 1: keyboard
> 5: NE2000 (only when the card was detected during boot)
> 19: 53c8xx
> no serial, parallel ports, no floppy (floppy seems to work fine though)

>
> /proc/pci shows:
>
> PCI devices found:
> Bus 0, device 11, function 0:
> IDE interface: CMD 646 (rev 1).
> Medium devsel. Fast back-to-back capable. IRQ 21. Master
Capable.
> Latency=32. Min Gnt=2.Max Lat=4.
> I/O at 0xb000.
> Bus 0, device 9, function 0:
> SCSI storage controller: NCR 53c810 (rev 17).
> Medium devsel. IRQ 19. Master Capable. Latency=32. Min
Gnt=8.Max
> Lat=64.
> I/O at 0xb400.
> Non-prefetchable 32 bit memory at 0x1000000.
> Bus 0, device 8, function 0:
> Non-VGA device: Intel 82378IB (rev 67).
> Medium devsel. Master Capable. No bursts.
> Bus 0, device 5, function 0:
> VGA compatible controller: S3 Inc. Trio32/Trio64 (rev 84).
> Medium devsel. IRQ 18.
> Non-prefetchable 32 bit memory at 0xc000000.
>
> What's the funny device 8
>
>
> Help on any of these things would be appreciated.
>
> Groeten,
> Geerten.
>
>
> Geerten Kuiper | "It is customary to append a signature or
> Corn. Houtmanstraat 113 | .sig to a mail message, usually containing
> 2593 RG Den Haag | information on the author, along with a
> Nederland | joke or a motto."
> | Olaf Kirch
> | LINUX Network Administrators Guide
>
> --
> To unsubscribe: send e-mail to axp-list-request@redhat.com with
> 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com

--
To unsubscribe: send e-mail to axp-list-request@redhat.com with
'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com



Feedback | Store | News | Support | Product Errata | About Us | Linux Info | Search | JumpWords
No Frames | Show Frames

Copyright © 1995-1997 Red Hat Software. Legal notices