LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-18-2013, 04:11 AM   #1
Jati
LQ Newbie
 
Registered: Sep 2013
Distribution: Slackware, Debian, Ubuntu, CentOS
Posts: 8

Rep: Reputation: Disabled
X2-compressed data is corrupt


Hi all, i got a problem when i upgrade my slackware kernel. i've compiled the kernel (3.11), and i dont update the lilo(when i update the lilo, the system miss the glibc). then i rebooted it. so i got this error when startup.

"X2-compressed data is corrupt
--system halted"

and the system hang.

here i use slackware64 14.

please help me
 
Old 09-18-2013, 06:27 AM   #2
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
When you don't update Lilo your new kernel will not be booted, it will start the old one. So your problem can't be a problem with the new kernel, but rather with your system, which is also indicated by the error you get regarding the missing glibc.
Is this the recommended full install?
 
Old 09-19-2013, 09:49 PM   #3
Jati
LQ Newbie
 
Registered: Sep 2013
Distribution: Slackware, Debian, Ubuntu, CentOS
Posts: 8

Original Poster
Rep: Reputation: Disabled
so, could i use my old kernel again? how to do that?

here the output of my error in GLIBC
Code:
#lilo
lilo: /lib/libc.so.6: version 'GLIBC_2.3' not found (required by lilo)
#
 
Old 09-19-2013, 10:46 PM   #4
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
When you have not removed your old kernel than lilo will boot that kernel if you don't upgrade lilo.
Regarding the glibc, do you by any chance have changed that also?
 
Old 09-19-2013, 11:10 PM   #5
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,783

Rep: Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214Reputation: 2214
A common cause of boot failure with lilo is that at some time in the (perhaps distant) past someone moved some of the boot files but did not re-run the lilo installer. The system can continue to boot just fine for quite a while because lilo is actually loading data that continues to exist in what is now marked as free space on the disk. Eventually, something new gets stored in some of those disk blocks, and suddenly the old, reliable kernel that you didn't change fails to boot.

Recovery requires booting from rescue media and running the lilo installer.
 
Old 09-20-2013, 03:27 AM   #6
Jati
LQ Newbie
 
Registered: Sep 2013
Distribution: Slackware, Debian, Ubuntu, CentOS
Posts: 8

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by TobiSGD View Post
When you have not removed your old kernel than lilo will boot that kernel if you don't upgrade lilo.
Regarding the glibc, do you by any chance have changed that also?
Quote:
Originally Posted by rknichols View Post
A common cause of boot failure with lilo is that at some time in the (perhaps distant) past someone moved some of the boot files but did not re-run the lilo installer. The system can continue to boot just fine for quite a while because lilo is actually loading data that continues to exist in what is now marked as free space on the disk. Eventually, something new gets stored in some of those disk blocks, and suddenly the old, reliable kernel that you didn't change fails to boot.

Recovery requires booting from rescue media and running the lilo installer.
actually i have replaced my old kernel configuration and i forgot to backup them.
then, for my question, can i place/install a new kernel or old kernel in my slackware in this situation?
should i use chroot?
 
Old 09-22-2013, 06:24 AM   #7
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
Quote:
Originally Posted by Jati View Post
actually i have replaced my old kernel configuration and i forgot to backup them.
then, for my question, can i place/install a new kernel or old kernel in my slackware in this situation?
should i use chroot?
Just install (or copy) a new kernel into the system, generate a new initrd, if necessary, chrrot into the system, update /etc/lilo.conf and run lilo.
 
Old 09-22-2013, 08:30 PM   #8
Jati
LQ Newbie
 
Registered: Sep 2013
Distribution: Slackware, Debian, Ubuntu, CentOS
Posts: 8

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by TobiSGD View Post
Just install (or copy) a new kernel into the system, generate a new initrd, if necessary, chrrot into the system, update /etc/lilo.conf and run lilo.
how to do that?
should i use slackware live cd?
or other distro isn't a problem?
 
Old 09-22-2013, 08:50 PM   #9
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
With the Slackware DVD it is easiest to do that, you don't even need to chroot, just follow the instructions on the bootloader's page of the DVD to boot the installed system, the just install/configure the system as you would do normally with your system.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] lzip compressed data arizonagroovejet Linux - General 2 03-15-2011 03:53 AM
invalid compressed data--format violated holland.d LinuxQuestions.org Member Success Stories 6 01-26-2010 05:31 PM
Linux Compressed ROM file data ?? maas187 Linux - Software 7 08-20-2008 10:42 AM
invalid compressed data error Seyfert Linux - Newbie 1 04-26-2006 03:47 PM
invalid compressed data crc--error aurelio26 Linux - Newbie 3 10-08-2004 02:53 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:19 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration