Re: [SOLVED] Prism 2.5 MiniPCI Wireless Unstable

2005-07-11 Thread Michael B Allen
ul 2005 01:46:52 +0300 Jar <[EMAIL PROTECTED]> wrote: > Michael B Allen wrote: > > hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen <[EMAIL PROTECTED]>) > > ACPI: PCI interrupt :02:02.0[A] -> GSI 11 (level, low) -> IRQ 11 > > hostap_pci: Registered netdevice

Re: Prism 2.5 MiniPCI Wireless Unstable

2005-07-11 Thread Michael B Allen
On Mon, 11 Jul 2005 17:08:38 +0300 (EEST) "Jar" <[EMAIL PROTECTED]> wrote: > > > FYI: > > > > Please use more suitable driver for 802.11b Prism cards. This kind of > > driver is > > hostap_pci (for PCI cards). It can be downloaded from > > http://hostap.epitest.fi/ > > > > This driver really wor

Prism 2.5 MiniPCI Wireless Unstable

2005-07-10 Thread Michael B Allen
My wireless is a little fragile. I have a Thinkpad T30 with a MiniPCI card: 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Intel Corp. Wireless 802.11b MiniPCI Adapter Flags: bus master, medium devsel, latency 64, IRQ 11 Memo

Re: parport not detected

2001-03-16 Thread Michael B. Allen
Yup! nano kernel: parport0: PC-style at 0x378, irq 7 [SPP,PS2,EPP] nano kernel: parport0: Printer, Hewlett-Packard HP LaserJet 6L I setup everything as you describe below. I don't remember having to do all this stuff before(on other machines anyway). I guess I'm used to RH's fluffed-up stock ke

parport not detected

2001-03-16 Thread Michael B. Allen
The parallel port is not being detected on my ABIT KT7A KT133 w/ Athlon 900 running 2.2.17 w/ Hendricks IDE patches and RH 6.2. I tried most of the settings in the bios. BIOS options are: 728/IRQ5 378/IRQ7 3BC/IRQ7 with the possible modes: Normal EPP 1.9 or 1.7 ECP DMA 3 or 1

xkill and do_try_to_free_pages

2001-02-23 Thread Michael B. Allen
Does this have to do with the thing that kills off processes when memory is low? Feb 23 04:39:32 nano kernel: VM: do_try_to_free_pages failed for xkill Maybe xkill should be something allowed to run? The app that I ran freaked(slrnconf) and snarfed up all my memory rapidly. If I could have kille

Re: 2.2.17 Lockup and ATA-66/100 forced bit set (WARNING)

2001-02-21 Thread Michael B. Allen
On Wed, Feb 21, 2001 at 03:48:06PM -0800, Wayne Whitney wrote: > > append="idebus=66 ide0=ata66" > > The idebus=66 part is incorrect. This option refers to the clock of > the PCI bus the IDE controller is on and should rarely be changed from > the default of 33MHz (i.e., only if you are overclo

2.2.17 Lockup and ATA-66/100 forced bit set (WARNING)

2001-02-21 Thread Michael B. Allen
I've enabled the higher performance features for my ATA drive by getting 2.2.17, applying Andre Hendrick's IDE patch, adding: append="idebus=66 ide0=ata66" to lilo.conf. I was told that Alan's patches from here: ftp.kernel.org/pub/linux/kernel/people/alan should be used. Is this true if I

Re: VIA chipset problems with 2.2?

2001-02-15 Thread Michael B. Allen
On Thu, Feb 15, 2001 at 06:33:36AM -0500, safemode wrote: > > What's the nature of the VIA chipset problems? I want to get a new system > > There are no problems with 2.2.x. I'm very glad to hear that because the AMD chips are the obvious choice for a lot of people(all?). > (classic), get the K

VIA chipset problems with 2.2?

2001-02-15 Thread Michael B. Allen
Hello, What's the nature of the VIA chipset problems? I want to get a new system this weekend but I read on kernel traffic that VIA has problems? I wan't to use Hendrick's ide patches on 2.2.18. What board should I get? Help, I've searched through usenet and asked on #linux without anything concl