Bug#523467: firmware-linux does not solve the problem

Alex Dănilă wrote: > Hi, > > CONFIG_X86_PAT is not set my 2.6.30 (that's my best knowledge; I > looked at .config file in the build directory made by kpkg). Adding > nopat boot option has no effect with neither local 2.6.30-rc3, nor > 2.6.30-rc5 from repository. nopat is useless if PAT is not enab

Bug#523467: firmware-linux does not solve the problem

Hi, CONFIG_X86_PAT is not set my 2.6.30 (that's my best knowledge; I looked at .config file in the build directory made by kpkg). Adding nopat boot option has no effect with neither local 2.6.30-rc3, nor 2.6.30-rc5 from repository. The firmware messages are like this (firmware-linux is inst

Bug#523467: firmware-linux does not solve the problem

Alex Dănilă wrote: > Hi, > > 2D continues to work well only with locally compiled 2.6.30 kernels, > but not with ones from Debian repository (2.6.29, 2.6.30) regardless > of the firmware-linux package. > > > No 2D: > 2.6.29 from repositories, with/without firmware-linux > 2.6.30 (rc1, rc3, rc5) fro

Bug#523467: firmware-linux does not solve the problem

Hi, 2D continues to work well only with locally compiled 2.6.30 kernels, but not with ones from Debian repository (2.6.29, 2.6.30) regardless of the firmware-linux package. No 2D: 2.6.29 from repositories, with/without firmware-linux 2.6.30 (rc1, rc3, rc5) from repositories, with/without fir