-Current kernels built with gcc 4.1?

shadowsnipes · 04-04-2008, 07:50 PM

I just installed -current from an install cd set I made using Alien's mirror-slackware-current.sh script.

I noticed that when I booted up to my fresh Slackware "12.1rc1" installation that none of my modules loaded. When I tried to build my module for my nvidia card it griped that the kernel was built with gcc 4.1 while gcc 4.2 is installed.

Has anyone else had this problem? Is it true -current's kernels where compiled with the old gcc? If so, why?

I know I can recompile the slackware kernels so that this isn't a problem. I'm just wondering if there was something I missed. Is there a gcc 4.2 version of these new kernel images and respective modules?

Again, I did not upgrade a previous version of slackware. I installed -current directly from cds made from my local mirror of -current (using Alien's nice script).

Thank you in advance for any help on this.

rworkman · 04-04-2008, 08:22 PM

Your local mirror is bad. No idea why :/

Bruce Hill · 04-04-2008, 08:41 PM

Confirm that ... I mirror from OSUOSL and have installed -current
with gcc-4.2.3 and 2.6.24.4 with no such problems. Silly question,
but do you check the md5sum of your CDs vs. iso images?

The present kernel is from the Mar 28 -current, and the update to
gcc-4.2.3 was on Feb 23.

shadowsnipes · 04-04-2008, 09:30 PM

Quote:

Originally Posted by rworkman

Your local mirror is bad. No idea why :/

Weird. I've never had problems with tds before. I used

Code:

slackware.mirrors.tds.net::slackware/

as specified in the script.

Quote:

Originally Posted by Bruce Hill

Confirm that ... I mirror from OSUOSL and have installed -current
with gcc-4.2.3 and 2.6.24.4 with no such problems. Silly question,
but do you check the md5sum of your CDs vs. iso images?

The present kernel is from the Mar 28 -current, and the update to
gcc-4.2.3 was on Feb 23.

I'll try a different mirror.

All my kernel packages are from the 26th and 27th and they are 2.6.24.4. I do have gcc-4.2.3.

Yes, I checked the md5sums of the packages using the MD5SUMS.TXT and I checked the md5sums of the iso images against that of my burned cds. All were good. I always have a script that does this in my PATH because I have seen a bad burn or two before.

Bruce Hill · 04-04-2008, 09:39 PM

This is what I use to check the md5sum of burned CD/DVDs:

Code:

To check the md5sum of a burned CD/DVD.

echo $(( $(ls -l /path/to/image.iso | awk '{ print $5 }') / 2048 ))
and use the block count with this command below:
dd if=/dev/hda bs=2048 count=2003361 | md5sum

I doubt the TDS mirror is bad, but it might not be
up-to-date.

Slackware -current is Fri Apr 4 13:47:24 CDT 2008

shadowsnipes · 04-04-2008, 09:50 PM

Quote:

Originally Posted by Bruce Hill

This is what I use to check the md5sum of burned CD/DVDs:

Code:

To check the md5sum of a burned CD/DVD.

echo $(( $(ls -l /path/to/image.iso | awk '{ print $5 }') / 2048 ))
and use the block count with this command below:
dd if=/dev/hda bs=2048 count=2003361 | md5sum

I doubt the TDS mirror is bad, but it might not be
up-to-date.

Slackware -current is Fri Apr 4 13:47:24 CDT 2008

Well I guess you showed me yours, so I'll show you mine.
This is my script
CkBurn2ISO.sh

Code:

#!/bin/sh
# This command will check the md5sum of a cd (ignoring possible padding at the end 
# by only checking the same amount of bytes at the iso image) and also check the 
# md5sum of the ISO image.

if [ $1 ]
then
        isoFile=$1
else
        echo "ERROR.  Usage: $0 /path/to/isofile.iso"
        exit 1
fi

echo $isoFile
if [ -e $isoFile ]
then
        dd if=/dev/hdd | head -c $(stat --format=%s $isoFile) | md5sum && md5sum $isoFile
else
        echo "ERROR.  ISO image at $isoFile does not exist."
        exit 1
fi

I just resync'd with the OSUOSL mirror. I forgot to switch on '-v' for verbose, so I don't know what what updated (except the new stuff in today's changelog).

I'm going to boot back into current now and 'upgradepkg --install-new' everything and see what happens.

shadowsnipes · 04-05-2008, 12:03 AM

I decided instead to just create some new ISOs and reinstall Slackware -current from them. I got the same results, however.

I even downloaded the kernel package from ftp.slackware.com and installed it. I went to a terminal and executed a 'uname -r' and I got back:
2.6.21.5! ... ! !! . . !!!

My .config under the linux sources says 2.6.24.4 and all my kernel images say that as well. Why does my system think it is a 2.6.21.5 kernel!?

Oh, and as far as I can tell the huge-smp kernel is from the 26th and some of the others are from the 27th. It says that on the TDS and ftp.slackware.com servers.

drumz · 04-05-2008, 12:07 AM

Did you forget to run lilo? Sometimes it's the simple things...

shadowsnipes · 04-05-2008, 12:28 AM

Quote:

Originally Posted by drumz

Did you forget to run lilo? Sometimes it's the simple things...

It's funny you say that. I took a few minutes away from the situation, and then I realized that it is probably a lilo misconfiguration.

part of my lilo.conf is:

Code:

image = /boot/vmlinuz
  root = /dev/hdb5
  append="mp3player=off"
  label = Slackware_Linux
  read-only  # Partitions should be mounted read-only for checking

image = /boot/vmlinuz
  root = /dev/hdb7
  label = Slack_Current
  read-only  # Partitions should be mounted read-only for checking

lilo.conf is on hdb5 with my main Slackware (12.0) install. Looks like I was booting my slackware 12.0 kernel.