Re: Cardbus conflicts...
> exclude port 0x2f8-0x2ff This exclusion is to block out the port range used by the IBM MWave DSP chip; this is your modem, not your sound card. Whatever your sound problem is, I don't think it is related to this specific item. I would recommend going to the linux-laptops site and checking out the pages devoted to the IBM TP 600E; it is likely that for a common model like this, people have put together detailed recipies for how to get sound, pcmcia, etc working. As for your specific questions, there are several better ways of handling this sort of thing automatically. If you build the PCMCIA drives with "PnP BIOS support" enabled, they will discover this and any other resource conflicts automatically. I think this option is also available in the newest 2.4.X kernels. PnP BIOS support is not enabled by default because there are compatibility problems on some systems. In the longer term ACPI support should also be able to handle this sort of conflict detection but I don't think it is sufficiently mature at this stage. -- Dave Hinds - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Cardbus conflicts...
exclude port 0x2f8-0x2ff This exclusion is to block out the port range used by the IBM MWave DSP chip; this is your modem, not your sound card. Whatever your sound problem is, I don't think it is related to this specific item. I would recommend going to the linux-laptops site and checking out the pages devoted to the IBM TP 600E; it is likely that for a common model like this, people have put together detailed recipies for how to get sound, pcmcia, etc working. As for your specific questions, there are several better ways of handling this sort of thing automatically. If you build the PCMCIA drives with PnP BIOS support enabled, they will discover this and any other resource conflicts automatically. I think this option is also available in the newest 2.4.X kernels. PnP BIOS support is not enabled by default because there are compatibility problems on some systems. In the longer term ACPI support should also be able to handle this sort of conflict detection but I don't think it is sufficiently mature at this stage. -- Dave Hinds - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Cardbus conflicts...
Evan Montgomery-Recht wrote: > > About 2 years ago, I bought a IBM 600E laptop with one > of the IBM branded Xircom CardBUS cards. It took me > about a month (with the help of a lot of people with > simular machines) to figure out why the card would be > recognized, and even connect to the network, but could > never get a IP address from DHCP. It turned out that > the sound card which is a one of the CS based chips. > The fix that I found was that if I added the following > line to the /etc/pcmcia/config.opts The card would be > detected, and recognized, and get a IP address. > > exclude ports 0x2f8-0x2ff What kernel are you running? You may need to go to http://pcmcia-cs.sourceforge.net/ for support, not there. For kernel 2.4, make sure you have the following options set, exactly as I present them, in your kernel .config file. CONFIG_PCMCIA=y CONFIG_CARDBUS=y # CONFIG_I82365 is not set -- Jeff Garzik | Disbelief, that's why you fail. Building 1024| MandrakeSoft | - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Cardbus conflicts...
About 2 years ago, I bought a IBM 600E laptop with one of the IBM branded Xircom CardBUS cards. It took me about a month (with the help of a lot of people with simular machines) to figure out why the card would be recognized, and even connect to the network, but could never get a IP address from DHCP. It turned out that the sound card which is a one of the CS based chips. The fix that I found was that if I added the following line to the /etc/pcmcia/config.opts The card would be detected, and recognized, and get a IP address. exclude ports 0x2f8-0x2ff The unfortunate side effect is that I cannot seem to get the sound card to work, even with OSS-commercial which I had a old license for that expires soon from when I bought a copy way back in I think 96' (what a scary thought). I realize that this this is a older machine, but this is not unique, I've found over the years that every machine I've owned has had a custom "profile" to get all addin-cards to work. So I leave with two questions. 1. Does someone have a better fix for this problem then I've been able to find? 2. It seems like there is a need to have like a "vendor-profile" support that allows for these special types of conflicts. I havn't been able to find much on this. Is anyone aware of such a thing. thanks, evan __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Cardbus conflicts...
About 2 years ago, I bought a IBM 600E laptop with one of the IBM branded Xircom CardBUS cards. It took me about a month (with the help of a lot of people with simular machines) to figure out why the card would be recognized, and even connect to the network, but could never get a IP address from DHCP. It turned out that the sound card which is a one of the CS based chips. The fix that I found was that if I added the following line to the /etc/pcmcia/config.opts The card would be detected, and recognized, and get a IP address. exclude ports 0x2f8-0x2ff The unfortunate side effect is that I cannot seem to get the sound card to work, even with OSS-commercial which I had a old license for that expires soon from when I bought a copy way back in I think 96' (what a scary thought). I realize that this this is a older machine, but this is not unique, I've found over the years that every machine I've owned has had a custom profile to get all addin-cards to work. So I leave with two questions. 1. Does someone have a better fix for this problem then I've been able to find? 2. It seems like there is a need to have like a vendor-profile support that allows for these special types of conflicts. I havn't been able to find much on this. Is anyone aware of such a thing. thanks, evan __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Cardbus conflicts...
Evan Montgomery-Recht wrote: About 2 years ago, I bought a IBM 600E laptop with one of the IBM branded Xircom CardBUS cards. It took me about a month (with the help of a lot of people with simular machines) to figure out why the card would be recognized, and even connect to the network, but could never get a IP address from DHCP. It turned out that the sound card which is a one of the CS based chips. The fix that I found was that if I added the following line to the /etc/pcmcia/config.opts The card would be detected, and recognized, and get a IP address. exclude ports 0x2f8-0x2ff What kernel are you running? You may need to go to http://pcmcia-cs.sourceforge.net/ for support, not there. For kernel 2.4, make sure you have the following options set, exactly as I present them, in your kernel .config file. CONFIG_PCMCIA=y CONFIG_CARDBUS=y # CONFIG_I82365 is not set -- Jeff Garzik | Disbelief, that's why you fail. Building 1024| MandrakeSoft | - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
