During the week, I tried to use the two kernels: 2.6.35.7 (compiled by
myself) and the 2.6.32-23 (from debian oficial mirror).
Using 2.6.35, no error occurred. But using 2.6.32, the error still happens.
And there was one time I used the 2.6.32, I turned off the computer and
turned it on using the
On Sun, 2010-10-03 at 15:32 -0300, Gilberto Segundo wrote:
> Hi!
>
> Sorry for the late. I had never compiled the kernel before. I compiled
> the kernel 2.6.35.7
>
> I followed the steps:
>
> 1 - Download and untar the kernel in /usr/src.
> 2 - # make localmodconfig
> 3 - INSTALL_MOD_STRIP=1 CO
Hi!
Sorry for the late. I had never compiled the kernel before. I compiled the
kernel 2.6.35.7
I followed the steps:
1 - Download and untar the kernel in /usr/src.
2 - # make localmodconfig
3 - INSTALL_MOD_STRIP=1 CONCURRENCY_LEVEL=3 fakeroot make-kpkg --initrd
--append-to-version=-i386-edps --r
HD:
ATA
SAMSUNG HD250HJ
I'm compiling the kernel 2.6.35.7 now. After I tell here the results.
On Sun, 2010-10-03 at 12:08 -0300, Gilberto Segundo wrote:
> Hello.
>
> I tested without the nvidia driver and the problem continues to
> happen.
>
> I did 3 tests:
>
> 1 - With Nvidia driver installed and using nvidia driver
> 2 - With Nvidia driver installed but using nv driver instead of nvid
On Sun, Oct 03, 2010 at 12:08:21PM -0300, Gilberto Segundo wrote:
> Hello.
>
> I tested without the nvidia driver and the problem continues to happen.
>
> I did 3 tests:
>
> 1 - With Nvidia driver installed and using nvidia driver
> 2 - With Nvidia driver installed but using nv driver instead of
Hello.
I tested without the nvidia driver and the problem continues to happen.
I did 3 tests:
1 - With Nvidia driver installed and using nvidia driver
2 - With Nvidia driver installed but using nv driver instead of nvidia
3 - With nvidia drver uninstalled and using nv driver. The lsmod does not
On Fri, 2010-10-01 at 10:37 -0300, Gilberto Segundo wrote:
> Today, I got the same error after the boot, more or less with three
> minutes in use.
>
> The filesystem is remounted read-only and the messages like that are
> showed (Dmesg did not save the log because the filesystem become read
> only
Today, I got the same error after the boot, more or less with three minutes
in use.
The filesystem is remounted read-only and the messages like that are showed
(Dmesg did not save the log because the filesystem become read only)
Aborting journal on device sda5-8.
EXT4-fs (sda5): Remounting filesy
9 matches
Mail list logo
