Re: Changing PCMCIA default resource ranges

2004-07-13 Thread Per Olofsson
Joey Hess wrote: > No initrd currently contains pcmcia-cs. Well, the initrd's on the CD images contain pcmcia-cs, but there's obviously no space problem there. > I think there is room on the net-drivers floppy, which is probably > the tightest image pcmcia-cs has to fit into. OK, good. -- Pell

Re: Changing PCMCIA default resource ranges

2004-07-12 Thread Joey Hess
Per Olofsson wrote: > Yes, indeed, it looks like it would work fine. It's 49K > though... 20K compressed. Is there space left on the initrd? No initrd currently contains pcmcia-cs. I think there is room on the net-drivers floppy, which is probably the tightest image pcmcia-cs has to fit into. > A

Re: Changing PCMCIA default resource ranges

2004-07-12 Thread Per Olofsson
Frans Pop wrote: > Someone on #d-boot mentioned that dmidecode could be used for that. Matthew Garrett wrote: > The DMI information that contains the manufacturer name can be > obtained from userspace with demidecode. Yes, indeed, it looks like it would work fine. It's 49K though... 20K compresse

Re: Changing PCMCIA default resource ranges

2004-07-11 Thread Frans Pop
On Sunday 11 July 2004 12:55, Per Olofsson wrote: > Joey Hess wrote: > > I suppose there's not a way to somehow autodetect these laptops by > > something else and change the resource range only there? > > The brand and model of the computer is included in a BIOS structure, > which is read by the ke

Re: Changing PCMCIA default resource ranges

2004-07-11 Thread Per Olofsson
Joey Hess wrote: > I've noticed the dell problems as well. I investigated this because you alerted me about it on IRC :) > I suppose there's not a way to somehow autodetect these laptops by > something else and change the resource range only there? The brand and model of the computer is included

Re: Changing PCMCIA default resource ranges

2004-07-10 Thread Cameron Patrick
On Sat, Jul 10, 2004 at 11:36:10AM -0400, Joey Hess wrote: > I've noticed the dell problems as well. I suppose there's not a way to > somehow autodetect these laptops by something else and change the > resource range only there? FWIW, it isn't just on Dell laptops -- my Dad's HP/Compaq laptop (Pr

Re: Changing PCMCIA default resource ranges

2004-07-10 Thread Joey Hess
Per Olofsson wrote: > There have been many reports of PCMCIA freezing during > installation. The reason for PCMCIA freezing is that the resource > ranges don't match the hardware. It's not possible to make the default > resource ranges work with all hardware (AFAIK) but I have noticed one > particu

Changing PCMCIA default resource ranges

2004-07-10 Thread Per Olofsson
There have been many reports of PCMCIA freezing during installation. The reason for PCMCIA freezing is that the resource ranges don't match the hardware. It's not possible to make the default resource ranges work with all hardware (AFAIK) but I have noticed one particularly problematic resource ran