Slackware-current Kernel OOPS
Hi @all,
I use slackware-current, the system works, but in dmesg I see this error: Code:
Write protecting the kernel read-only data: 16384k greets fl0 |
Which version of the kernel are you using? The latest slackware-current kernel was updated yesterday (5/1/2010) to 2.6.33.3.
|
Hi,
I set up the Laptop Today... Code:
flo@hydra:~$ uname -a |
Which kernel are you using? Huge, generic or a custom built one?
|
If you are using the generic kernel, you need to use an initrd. If I'm right, then you need to do the following:
1. Login or switch to root. 2. cd /boot 3. mkinitrd -c -k 2.6.33.3 -m ext4 4. Edit /etc/lilo.conf and add the following line below the image = /boot/vmlinuz line: initrd = /boot/initrd.gz 5. Run 'lilo' to load your updated lilo.conf file. 6. Reboot |
ok...
I use crypto and lvm (following this how to http://ftp.gwdg.de/pub/linux/slackwa...ADME_CRYPT.TXT) it is the generic kernel and I use a initrd. |
I don't use crypto or lvm, but in the -current changelog, there have been some recent changes to lvm and crypto related packages. Maybe that has something to do with it.
Quote:
Quote:
|
Any chance you might be trying to use an initrd to load ext4 modules into the huge kernel (which already has ext4 built-in)? The error messages about -EEXIST suggest that possibility.
|
Quote:
|
Quote:
|
Quote:
|
All times are GMT -5. The time now is 10:46 AM. |