Re: Corrupted Hard Drive after activating intel I/oat dma
Marek Kierdelewicz wrote: I'm a [EMAIL PROTECTED] user myself. This distro is very disk-demanding because of the frequent compilations. In my opinion it's not the best distro for a mobile system. No wonder your disk gave out :(. Can you substantiate "distro is very disk-demanding because of the frequent compilations" ? -- Shourya Sarcar sarcarsh at gmail spot com http://shouryalive.com/blog -- 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: Corrupted Hard Drive after activating intel I/oat dma
Marek Kierdelewicz wrote: I'm a [EMAIL PROTECTED] user myself. This distro is very disk-demanding because of the frequent compilations. In my opinion it's not the best distro for a mobile system. No wonder your disk gave out :(. Can you substantiate distro is very disk-demanding because of the frequent compilations ? -- Shourya Sarcar sarcarsh at gmail spot com http://shouryalive.com/blog -- 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: Boot time module loading problem
Larry Finger wrote: With 2.6.24-rc5, a b43 user reports a problem at bootup. The b43 module, which should be loaded by the ssb module, fails with the following type of message: ssb: Sonics Silicon Backplane found on PCI device :0c:00.0 b43: disagrees about version of symbol ssb_device_is_enabled b43: Unknown symbol ssb_device_is_enabled b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable b43: disagrees about version of symbol ssb_bus_may_powerdown b43: Unknown symbol ssb_bus_may_powerdown < and more similar lines> If the user issues the commands rmmod ssb; modprobe b43 then the modules are loaded correctly and the wireless device works. What could be causing such a problem? Larry Larry, thanks for pursuing this. I upgraded to 2.6.24-rc6 last night and I don't see this issue anymore. One might think that the clean remake solved the problem (which I am pretty sure I did with rc5 as well); but still does not explain with 2.6.24-rc5, the module would not load on first attempt but then load after the manual: # rmmod ssb;modprobe b43 Best regards, Shourya -- 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: Boot time module loading problem
Larry Finger wrote: With 2.6.24-rc5, a b43 user reports a problem at bootup. The b43 module, which should be loaded by the ssb module, fails with the following type of message: ssb: Sonics Silicon Backplane found on PCI device :0c:00.0 b43: disagrees about version of symbol ssb_device_is_enabled b43: Unknown symbol ssb_device_is_enabled b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable b43: disagrees about version of symbol ssb_bus_may_powerdown b43: Unknown symbol ssb_bus_may_powerdown and more similar lines If the user issues the commands rmmod ssb; modprobe b43 then the modules are loaded correctly and the wireless device works. What could be causing such a problem? Larry Larry, thanks for pursuing this. I upgraded to 2.6.24-rc6 last night and I don't see this issue anymore. One might think that the clean remake solved the problem (which I am pretty sure I did with rc5 as well); but still does not explain with 2.6.24-rc5, the module would not load on first attempt but then load after the manual: # rmmod ssb;modprobe b43 Best regards, Shourya -- 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/
