LinuxQuestions.org - Squeeze to wheeze update

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Squeeze to wheeze update (https://www.linuxquestions.org/questions/linux-newbie-8/squeeze-to-wheeze-update-4175472803/)

Squeeze to wheeze update

Hi everyone!
As a newbie I tried to update my squeeze to wheezy, and now I only have a console. This console doesn't even have internet access. Then I run dhclient eth0. Then I do apt-get update, and every time I try apt-get upgrade I get seomthing like

Import error libapt-pkg.so.4.12 No such file or directory.

I tried with apt-get -f install, but that doesn't work either.
Sometimes I get the message

error file /var/lib/dpkg/status package arm-compiler-none-aabi

What did I do? well, I followed the steps I found in
http://www.howtoforge.com/how-to-upg...eeze-to-wheezy
I just copy and paste the sources.list file. I was wondering if it was trying to install wheezy 64bits, when I had squeeze 32 bits, I hope it wasn't.

any ideas of what should I do?
:o

I downloaded the package libapt-pkg4.12_0.9.7.9_i386.deb from http://pkgs.org/debian-wheezy/debian....deb/download/ and typed dpkg -i libapt.... and I got dpkg error: parsing file /var/lib/dpkg/status near package 'arm-compiler-non-eabi: blank line of field 'Description'

Did you follow the rest of the steps in the article: to backup crucial dats, then update your system, then run apt-get dist-upgrade, etc.?

Offhand, I would suggest that you first back up any crucial data on that machine to external media before you try to troubleshoot this further.

Hi there!

I opened the file /var/lib/dpkg/status and deleted the section related with the package arm-compiler-none-aabi.

after that everything went well and at the end I had a console again. Then I went to aptitude and pressed "g", but there's a moment when it says that currently I have the kernel 2.6.32-5-686 and it says that it is trying to delete it, and that that action will make the system unbootable. I always selected "abort". Now my system is working, I have gnome 3, but I guess the kernel is the same that I had before, besides that, I wonder about this:

root@mrp-prettydesk:/home/joc/Downloads# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.1 (wheezy)
Release: 7.1
Codename: wheezy

Is it ok if it says "No LSB modules are available"? Will I have any troubles in the future?
and the next question is, should I update the kernel? if so, how?
Or should I ask this questions in another thread?

Thanks in advance
/Joc

Squeeze to wheeze update

My 2 cents: back up any data you want to keep to an external storage device, format your debian partition, and install debian wheezy from scratch. If you're being told your kernel is going to be deleted etc it sounds like that would be the most painless thing to do unfortunately! I imagine that isnt what you wanted to hear though

What is the output of uname -a. Mine outputs a v. 3 kernel.

I was just looking at /boot/grub on my Wheezy machine. It looks like the update included a jump from grub-legacy to Grub 2.

My menu.lst list of kernels stops with a v. 2.6.x kernel and includes a command to chainload to grub 2.

The grub.cfg includes the current list of kernels.

What are the outputs the following commands?

Code:

cat /boot/grub/menu.lst

Code:

cat /boot/grub/grub.cfg

Be sure to surround it with "code" tags, which become available when you click the "Go Advanced" button at the bottom of the quick reply window.

I think it's possible that the grub 2 install may have gone screwy. That's just a guess, but I think it's worth investigating.

let me see

Quote:

uname -a
Linux mrp-prettydesk 2.6.32-5-686 #1 SMP Fri May 10 08:33:48 UTC 2013 i686 GNU/Linux

I should mention that this computer had originally windows, then I made a partition and installed debian 32bits. Two weeks ago I needed to install a software that only runs on 64bits machines, and I did another partition with Debian 64 bits, and since it looked good too me, I tried to update the partition with Debian 32 bits. The reason I haven't switched completely to 64 bits, is that I have another software that only runs on 32 bits.

Anyway for the menu.lst I got

Quote:

cat /boot/grub/menu.lst
cat: /boot/grub/menu.lst: No such file or directory

and for grub.cfg

Quote:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root e0ff680a-5cc8-4dec-9aec-28d8b00216a2
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root e0ff680a-5cc8-4dec-9aec-28d8b00216a2
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root e0ff680a-5cc8-4dec-9aec-28d8b00216a2
insmod png
if background_image /usr/share/images/desktop-base/joy-grub.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root e0ff680a-5cc8-4dec-9aec-28d8b00216a2
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=e0ff680a-5cc8-4dec-9aec-28d8b00216a2 ro vga=769 quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root e0ff680a-5cc8-4dec-9aec-28d8b00216a2
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=e0ff680a-5cc8-4dec-9aec-28d8b00216a2 ro single vga=769
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Dell Utility Partition (on /dev/sda1)" --class windows --class os {
insmod part_msdos
insmod fat
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 07D7-0517
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry "Microsoft Windows XP Professional (on /dev/sda2)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root 72D85D26D85CE9BD
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry "Debian GNU/Linux, with Linux 3.2.0-4-amd64 (on /dev/sda4)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set=root fb70ebbe-c9ff-46e9-8c25-dbd18e0926fc
linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=fb70ebbe-c9ff-46e9-8c25-dbd18e0926fc ro quiet
initrd /boot/initrd.img-3.2.0-4-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.2.0-4-amd64 (recovery mode) (on /dev/sda4)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set=root fb70ebbe-c9ff-46e9-8c25-dbd18e0926fc
linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=fb70ebbe-c9ff-46e9-8c25-dbd18e0926fc ro single
initrd /boot/initrd.img-3.2.0-4-amd64
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

Thanks in advance.
/orcaja

I'm guessing here, since I've never had to deal with a problem like this, but I see that your grub.cfg has references to v. 3.x kernels. According I don't understand why it would be trying to boot to the 2.6.x kernel.

Trying to troubleshoot this further is beyond my skill level, but I think the fruitful course of action is to determine why the system is not booting to the 3.2.0-4-amd64 kernel. Running ls /boot might be a start.

You might also check this article from the Ubuntu website:

https://help.ubuntu.com/community/Grub2/Troubleshooting

I believe that when Grub starts, it gives you a chance to press "e" to edit (it's been a while, since Slackware uses Lilo and I seldom reboot my Debian box). I would start there.

Let's hope that someone who knows what he's doing comes along and helps us both.

Since you installed 64-bit last I would boot to it & run update-grub which should do it.