Slackware-current upgrades today.

fogpipe · 12-22-2012, 01:31 PM

Is it just me or does the 3.7 kernel seem faster than the old one?
It might also be that i hadnt rebooted in a couple of months, but things seem snappier generally.

T3slider · 12-22-2012, 01:34 PM

Quote:

Originally Posted by cwizardone

Appears to have better support for HDMI audio (off of my Nvidia graphics card). KDE actually automatically found it and used it, but there is still no volume control. I think it woke up everyone in the house.

I would expect volume control to be confined to the receiver. If you want volume control over HDMI output then you'd need to implement a software volume control. This is not a bug IMO.

cwizardone · 12-22-2012, 01:41 PM

Quote:

Originally Posted by T3slider

I would expect volume control to be confined to the receiver. If you want volume control over HDMI output then you'd need to implement a software volume control. This is not a bug IMO.

Ba-hum-bug, I didn't say it was a bug.

Perhaps, I should have said the KDE mixer doesn't control it, and, yes, I'm aware you have to use software control with various applications. Regardless, I went back to the built-in audio card on the motherboard. Easier to control with the KDE or Xfce mixer.

willysr · 12-22-2012, 06:06 PM

Quote:

Originally Posted by fogpipe

Just upgraded and the old nvidia version i was using wouldnt compile because it was looking for a "version.h" in the kernel source that wasnt there.

If you have an nvidia card, save yourself a headache and download the latest nvidia driver for your card before that first reboot.

Try this one

Code:

ln -s /usr/src/linux-3.7/include/generated/uapi/linux/version.h /usr/src/linux-3.7/include/linux/version.h

If you used older NVidia driver, you would need a patch described on my Blog

tux_dude · 12-23-2012, 12:04 AM

Quote:

Originally Posted by Neil65

Okay, so I have a customized boot CD so I just plucked the new kernel and the new /lib/modules/
Everything is good booting up from USB but now my usb stick is /dev/sda and the sata hard-drive is /dev/sdb which is the opposite of before. Has anyone else seen this or is this just a feature of the newer kernels? ...

What is the official word on this? I notice a similar issue with my RC7 kernel on my usb drive which I use for resizing the volumes > 16TB. My OS drive that is on the sata_0 on the motherboard has always been sda. With RC7 it was no longer sda. I have not dug into it, but it seems the HBA drives are assigned before the onboard sata dirves. I'll be updating my usb drive, but cannot test until I have another resize to perform.

fogpipe · 12-23-2012, 06:53 AM

Quote:

Originally Posted by willysr

Try this one

Code:

ln -s /usr/src/linux-3.7/include/generated/uapi/linux/version.h /usr/src/linux-3.7/include/linux/version.h

If you used older NVidia driver, you would need a patch described on my Blog

Actually upgrading the driver worked fine, thats good to know tho.

audriusk · 12-23-2012, 07:01 AM

Quote:

Originally Posted by tux_dude

What is the official word on this? I notice a similar issue with my RC7 kernel on my usb drive which I use for resizing the volumes > 16TB. My OS drive that is on the sata_0 on the motherboard has always been sda. With RC7 it was no longer sda. I have not dug into it, but it seems the HBA drives are assigned before the onboard sata dirves. I'll be updating my usb drive, but cannot test until I have another resize to perform.

AFAIK this behavior is normal for recent kernels (since the switch to SATA subsystem for all hard drives?), it's also unavoidable. If you want to be sure that the right device is mounted on the right mount point, use labels or UUIDs. Look them up using

Code:

lsblk -f

and in your /etc/fstab first column write LABEL=actual-label or UUID=actual-uuid instead of path to device.

lkraemer · 12-23-2012, 07:24 AM

I'm new enough I don't understand the fix for this issue.

Quote:

Originally Posted by W4LK:
I tried to install the upgrades today and it failed with bad MD5 sums. What's the fix?

Quote:

Originally Posted by hitest:
Try running slackpkg upgrade-all again and re-install any files that had bad md5 sums.

Quote:

Originally Posted by W4LK:
Slackpkg reports all md5's are bad....I downloaded the files manually and installed them manually with no problems.
Not quite sure how to upgrade the new initrc.img file. It is not a .tgz format. I was able to make a init.gz for the
new kernel which works fine.

I still have the following warnings:

Code:

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:                       

binutils-2.23.51.0.6-i486-1.txz:	md5sum
gcc-4.7.2-i486-1.txz:	md5sum
gcc-g++-4.7.2-i486-1.txz:	md5sum
gcc-gfortran-4.7.2-i486-1.txz:	md5sum
gcc-gnat-4.7.2-i486-1.txz:	md5sum
gcc-go-4.7.2-i486-1.txz:	md5sum
gcc-java-4.7.2-i486-1.txz:	md5sum
gcc-objc-4.7.2-i486-1.txz:	md5sum
kernel-headers-3.7.1_smp-x86-1.txz:	md5sum
kernel-modules-3.7.1-i486-1.txz:	md5sum
kernel-modules-smp-3.7.1_smp-i686-1.txz:	md5sum
kernel-source-3.7.1_smp-noarch-1.txz:	md5sum
oprofile-0.9.7-i486-3.txz:	md5sum

==============================================================================

And since I'm still a novice without the following knowledge:
1. Where do I download the files with bad MD5SUM's?
2. How do I manually install them?
3. How do I make a new init.gz file for the kernel?

Somehow I've missing this information...

Thanks.

Larry

escaflown · 12-23-2012, 02:21 PM

Quote:

Originally Posted by lkraemer

I'm new enough I don't understand the fix for this issue.

And since I'm still a novice without the following knowledge:
1. Where do I download the files with bad MD5SUM's?
2. How do I manually install them?
3. How do I make a new init.gz file for the kernel?

Somehow I've missing this information...

Thanks.

Larry

Try another mirror in the slackpkg mirror file (/etc/slackpkg/mirrors). I had the same issue and I ended up using the kernel.org mirror ( ftp://mirrors.us.kernel.org/slackwar...kware-current/), which solved the issue.

stormtracknole · 12-23-2012, 02:54 PM

Quote:

Originally Posted by fogpipe

Is it just me or does the 3.7 kernel seem faster than the old one?
It might also be that i hadnt rebooted in a couple of months, but things seem snappier generally.

I have noticed that my netbook runs much cooler under this kernel.

lkraemer · 12-23-2012, 03:33 PM

escaflown,
THANKS for the TIP. I had a situation where I couldn't boot from the Hard Drive. I was beginning to Panic.
I finally got it working. For others with the same condition, here is what I did.

Assuming you have Ethernet Cable connection, I did the following:
1. Booted form my Slackware 14 DVD
2. Logged in as root
3. chroot into my system

Code:

    mkdir /mnt/centon
    mount /dev/sda1 /mnt/centon
    mount --bind /proc /mnt/centon/proc
    mount --bind /sys /mnt/centon/sys
    mount --bind /dev /mnt/centon/dev
    chroot /mnt/centon
    nano /etc/slackpkg/mirrors
## scrolled down to find the mirror I had enabled, then replaced it with:
## ftp://mirrors.us.kernel.org/slackware/slackware-current/
## Saved the file with CNTL O
    lilo
    exit
    reboot

Now I'm happy,happy,happy.

THANKS.

Larry

Neil65 · 12-23-2012, 03:37 PM

Quote:

Originally Posted by audriusk

AFAIK this behavior is normal for recent kernels (since the switch to SATA subsystem for all hard drives?), it's also unavoidable. If you want to be sure that the right device is mounted on the right mount point, use labels or UUIDs. Look them up using

Code:

lsblk -f

and in your /etc/fstab first column write LABEL=actual-label or UUID=actual-uuid instead of path to device.

No, this is definitely new behavior since 3.2.x, and I got rid of the IDE native drivers long before then. Besides, its USB drives that are jumping to the head of the queue and they have always been in the scsi namespace. I've googled for the cause and haven't found anything, though I think Slackware is ahead of the curve when it comes to new OSs on bootable USB images. Just waiting for more poo to hit some bigger fans.

I can fix the symptom but I'd rather not have too. This is similar to randomized NICs have been a source of joy for a while. Though I suppose more checks before an fdisk isn't all bad.