LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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
 
LinkBack Search this Thread
Old 12-22-2012, 01:31 PM   #16
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 Current
Posts: 313

Rep: Reputation: 64

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.
 
Old 12-22-2012, 01:34 PM   #17
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.0
Posts: 2,231

Rep: Reputation: 573Reputation: 573Reputation: 573Reputation: 573Reputation: 573Reputation: 573
Quote:
Originally Posted by cwizardone View Post
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.
 
Old 12-22-2012, 01:41 PM   #18
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,095

Rep: Reputation: 147Reputation: 147
Quote:
Originally Posted by T3slider View Post
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.

Last edited by cwizardone; 12-22-2012 at 01:42 PM.
 
Old 12-22-2012, 06:06 PM   #19
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,344

Rep: Reputation: 377Reputation: 377Reputation: 377Reputation: 377
Quote:
Originally Posted by fogpipe View Post
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
 
Old 12-23-2012, 12:04 AM   #20
tux_dude
Member
 
Registered: Dec 2008
Distribution: Slackware64 Current
Posts: 222

Rep: Reputation: 33
Quote:
Originally Posted by Neil65 View Post
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.
 
Old 12-23-2012, 06:53 AM   #21
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 Current
Posts: 313

Rep: Reputation: 64
Quote:
Originally Posted by willysr View Post
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.
 
Old 12-23-2012, 07:01 AM   #22
audriusk
Member
 
Registered: Mar 2011
Location: Klaipėda, Lithuania
Distribution: Slackware
Posts: 231

Rep: Reputation: 102Reputation: 102
Quote:
Originally Posted by tux_dude View Post
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.
 
Old 12-23-2012, 07:24 AM   #23
lkraemer
Member
 
Registered: Aug 2008
Posts: 111

Rep: Reputation: 10
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
 
Old 12-23-2012, 02:21 PM   #24
escaflown
Member
 
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 235

Rep: Reputation: 30
Quote:
Originally Posted by lkraemer View Post
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.
 
Old 12-23-2012, 02:54 PM   #25
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 779

Rep: Reputation: 103Reputation: 103
Quote:
Originally Posted by fogpipe View Post
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.
 
Old 12-23-2012, 03:33 PM   #26
lkraemer
Member
 
Registered: Aug 2008
Posts: 111

Rep: Reputation: 10
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

Last edited by lkraemer; 12-23-2012 at 05:20 PM.
 
Old 12-23-2012, 03:37 PM   #27
Neil65
LQ Newbie
 
Registered: Jul 2012
Posts: 8

Rep: Reputation: Disabled
Quote:
Originally Posted by audriusk View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Less backlight steps after current upgrades brodo Slackware 3 07-29-2012 12:40 PM
Wine & the latest current upgrades problem /32-bit/ brodo Slackware 12 11-27-2010 05:12 AM
libgmp and libpng in latest -current upgrades dive Slackware 37 03-05-2010 11:40 AM
Slackware current updates today! neo Slackware 2 04-22-2005 05:32 PM


All times are GMT -5. The time now is 01:38 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration