Oops at boot with 2.4.5

overclocked) on an MSI K7T Turbo-R motherboard. I've worked around this by building my SCSI driver into the kernel and removing the need for an initrd. Kernel is official 2.4.5 built with Athlon optimizations. -- Manuel A. McLure - Unify Corp. Technical Support <[EMAIL PROTECTED]> Zathra

RE: Still IRQ routing problems with VIA

Q even if XFree86/Linux doesn't. I dunno if Windows is smart enough to assign an IRQ even if the BIOS doesn't. Anyway, things are working now (specially since the last tulip patches) and I like it that way :-) -- Manuel A. McLure - Unify Corp. Technical Support <[EMAIL PROTECTED]>

RE: Still IRQ routing problems with VIA

as some additional information. Here's my dmesg output - I tried with both PNP: Yes and PNP: No and the dmesg outputs were exactly the same modulo a Hz or two in the processor speed detection. I do have an IRQ for my VGA since the instructions for my card (a Voodoo 5 5500) specifically say an I

RE: Still IRQ routing problems with VIA

Axel Thimm said... > On Tue, Apr 10, 2001 at 09:51:18AM -0700, Manuel A. McLure wrote: > > I have the same motherboard with the same lspci output > (i.e. I get the "pin > > ?" part), but I don't see any problems running 2.4.3 or > 2.4.3-ac[23]. I am >

RE: Still IRQ routing problems with VIA (was: VIA KT133 chipset PCI crazyness...)

iated! My board wants to run 2.4.x!!! > > BTW kernel 2.2.x does not give any irq related messages in > its logs. Does this > mean that 2.2.x works well, or that the errors are just not displayed? > > Thanks, Axel. > -- > [EMAIL PROTECTED] > I have the same motherboard wit

RE: tulip (was RE: Kernel 2.4.3 fails to compile)

Jeff Garzik said: [snip conversation about NETDEV WATCHDOG errors on ADMTek Comet tulip clone card] > > Ok, this should be fixed in the latest patches sent to Alan and Linus. Testing with 2.4.3-ac3 and so far, so good. Thanks! -- Manuel A. McLure - Unify Corp. Technical Support &

RE: tulip (was RE: Kernel 2.4.3 fails to compile)

Jeff Garzik wrote: > On Fri, 30 Mar 2001, Manuel A. McLure wrote: > > It looks like the tulip driver isn't as up-to-date as the one from > > 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV > WATCHDOG errors shortly > > after rebooting with 2.4.3, although thes

RE: Kernel 2.4.3 fails to compile

Jeff Garzik wrote: > On Fri, 30 Mar 2001, Manuel A. McLure wrote: > > > Jeff Garzik wrote: > > > On Fri, 30 Mar 2001, Manuel A. McLure wrote: > > > > > > > ... > > > > gcc -D__KERNEL__ -I/usr/src/linux/include -Wall > > > -

RE: Kernel 2.4.3 fails to compile

Jeff Garzik wrote: > On Fri, 30 Mar 2001, Manuel A. McLure wrote: > > > ... > > gcc -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -O2 > > -fomit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 > > -march=ath

Kernel 2.4.3 fails to compile

not set # CONFIG_USB_SERIAL_MCT_U232 is not set CONFIG_USB_SERIAL_OMNINET=m # # USB misc drivers # CONFIG_USB_RIO500=m # # Kernel hacking # # CONFIG_MAGIC_SYSRQ is not set -- Manuel A. McLure - Unify Corp. Technical Support <[EMAIL PROTECTED]> Space Ghost: "Hey, what happened to the

RE: NETDEV WATCHDOG: eth0: transmit timed out on LNE100TX 4.0, kernel2.4.2-ac11 and earlier.

ttl=255 time=361 usec 64 bytes from leng.internal.mclure.org (10.1.1.1): icmp_seq=15 ttl=255 time=395 usec So the behavior is quite a bit better (at least I can telnet in to ifdown/ifup) but still not OK. Once again, ifdown/ifup makes things work OK. Thanks! -- Manuel A. McLure - Unify Corp. Technical Support &l

NETDEV WATCHDOG: eth0: transmit timed out on LNE100TX 4.0, kernel 2.4.2-ac11 and earlier.

thar kernel: PCI: The same IRQ used for device 00:0e.0 Mar 12 21:38:49 ulthar kernel: eth0: ADMtek Comet rev 17 at 0xdc00, 00:20:78:0D: D2:E1, IRQ 11. Any ideas on why this might be happening? -- Manuel A. McLure - Unify Corp. Technical Support <[EMAIL PROTECTED]> Space Ghost: "Hey, what