colin setup and fine tuning quest

[dkeg]

tried booting with init. no diff. my bloat spin upg systemd already.
@MB

Code: Select all

[10:47]─[~]
└──╼ policy linux-image-3.10-3-686-pae linux-headers-3.10-3-686-pae
linux-image-3.10-3-686-pae:
  Installed: 3.10.11-1
  Candidate: 3.10.11-1
  Version table:
 *** 3.10.11-1 0
        500 http://http.us.debian.org/debian/ unstable/main i386 Packages
        100 /var/lib/dpkg/status
linux-headers-3.10-3-686-pae:
  Installed: 3.10.11-1
  Candidate: 3.10.11-1
  Version table:
 *** 3.10.11-1 0
        500 http://http.us.debian.org/debian/ unstable/main i386 Packages
        100 /var/lib/dpkg/status

[machinebacon]

Can you purge the non-PAE siduction kernel so that it runs update-initramfs or do the

Code: Select all

sudo update-initramfs -c -k 3.10-3-686-pae
sudo update-grub

again?

Of course, post the output. Seems that something is missing there.

Edit: typofixing

[machinebacon]

Of course, you can update all of them with sudo update-initramfs -u

[dkeg]

[10:58]─[~]
└──╼ sudo update-initramfs -c -k initrd.img-3.10-3-686-pae
[sudo] password for dkeg:
update-initramfs: Generating /boot/initrd.img-initrd.img-3.10-3-686-pae
WARNING: missing /lib/modules/initrd.img-3.10-3-686-pae
Device driver support needs thus be built-in linux image!
FATAL: initrd.img-3.10-3-686-pae: not absolute path.

hmm, interesting.

[machinebacon]

remove the newly created file in /boot (it is something with a long filename*) and do the update-initramfs -u

(* /boot/initrd.img-initrd.img-3.10-3-686-pae)

[xaos52]

Code: Select all

sudo update-initramfs -c -k initrd.img-3.10-3-686-pae

is wrong.
Should be -k 3.10-3-686-pae

[dkeg]

Brb.... taking kids to preschool.

[dkeg]

nothing is working and I think this is the main issue. I purged the 3.10 vanilla kernel

Code: Select all

The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz 
You may need to re-run your boot loader
The link /initrd.img is a damaged link
Removing symbolic link initrd.img 
You may need to re-run your boot loader

aren't these links created automatically during install?

[xaos52]

Depends on the distro.
If the links are damaged, you can remove and recreate them: e.g. to create a link /vmlinuz in the root directory to a kernel image /boot/vmlinuz-3.1.2-amd64 you would enter the command - as root:

Code: Select all

ln -sf /boot/vmlinuz-3.11.2-amd64 vmlinuz

while you are in the root directory.
Check with ls -al /
There should be an entry
/vmlinuz -> /boot/vmlinuz-3.11.2-amd64

[dkeg]

guys, thanks so much for assisting.

Nothing is working. It is seeming like at modprobe is when the issue is occuring. I could see it didn't like a line in which I recognized from /etc/modprobe.d/alsa-base.conf, got rid of that, but now something else bugs it out.

I'll revisit this another time. For now, I'm putting this to rest. We move this weekend. Maybe once we settle a bit.