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
 
Search this Thread
Old 02-02-2014, 10:49 AM   #1
NikolaStanchev
LQ Newbie
 
Registered: Feb 2014
Distribution: Slackware14.1
Posts: 12

Rep: Reputation: Disabled
Switch to generic kernel - unsuccessful


Hi, everyone! I am sorry in advance for my incompetence but i am stuck. I also know the fact that there are similar threads, for which i apologize one more time but i have project to work on and without solving this problem it will be hard to continue. I am running Slackware 14.1; kernel version 3.10.17. I installed it 2 days before and wanted to switch to the generic kernel but after i tried to do this, my system refused to boot the generic kernel. Running mkinitrd - getting this
Code:
ls: cannot access /sys/module/*_hcd/drivers/*: No such file or directory
Please help! Than you very much!
 
Old 02-02-2014, 11:47 AM   #2
Bertman123
Member
 
Registered: Jun 2010
Distribution: Slackware
Posts: 204

Rep: Reputation: 28
Switching to a generic kernel isn't too difficult, but can be challenging the first time you attempt it.

This first link helped me a lot in figuring it out.

http://mirrors.slackware.com/slackwa.../README.initrd

Make sure you install the three packages below (the generic kernel is probably already installed, but I installed it again anyway just to be safe). Once these packages are installed you can either follow the instructions in the link above, or the instructions in the link below - about half way down the page.

kernel-generic-smp-3.10.17_smp-i686-3.txz
kernel-modules-smp-3.10.17_smp-i686-3.txz
mkinitrd-1.4.8-i486-1.txz


http://docs.slackware.com/slackware:beginners_guide
 
Old 02-02-2014, 12:01 PM   #3
NikolaStanchev
LQ Newbie
 
Registered: Feb 2014
Distribution: Slackware14.1
Posts: 12

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Bertman123 View Post
Switching to a generic kernel isn't too difficult, but can be challenging the first time you attempt it.

This first link helped me a lot in figuring it out.

http://mirrors.slackware.com/slackwa.../README.initrd

Make sure you install the three packages below (the generic kernel is probably already installed, but I installed it again anyway just to be safe). Once these packages are installed you can either follow the instructions in the link above, or the instructions in the link below - about half way down the page.

kernel-generic-smp-3.10.17_smp-i686-3.txz
kernel-modules-smp-3.10.17_smp-i686-3.txz
mkinitrd-1.4.8-i486-1.txz


http://docs.slackware.com/slackware:beginners_guide
Will this solve this poblem?
 
Old 02-02-2014, 01:40 PM   #4
55020
Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 347
Blog Entries: 4

Rep: Reputation: 310Reputation: 310Reputation: 310Reputation: 310
I understand from the other thread that you are using mkinitrd_command_generator.sh, not mkinitrd.

Here are two solutions.

(1) If you do not have LVM or LUKS or raid partitions, and you don't boot from a USB device, use mkinitrd - it's not difficult. See the file /boot/README.initrd .

or

(2) If you do have LVM or LUKS or raid partitions, but you don't boot from a USB device, edit /usr/share/mkinitrd/mkinitrd_command_generator.sh to comment out lines 453-455
Code:
# If we use any USB module, try to determine the Host Controller
# if echo $MLIST | grep -q "usb"; then
#   MLIST=$(add_usb_hcd)
# fi
 
1 members found this post helpful.
Old 02-02-2014, 02:31 PM   #5
NikolaStanchev
LQ Newbie
 
Registered: Feb 2014
Distribution: Slackware14.1
Posts: 12

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by 55020 View Post
I understand from the other thread that you are using mkinitrd_command_generator.sh, not mkinitrd.

Here are two solutions.

(1) If you do not have LVM or LUKS or raid partitions, and you don't boot from a USB device, use mkinitrd - it's not difficult. See the file /boot/README.initrd .

or

(2) If you do have LVM or LUKS or raid partitions, but you don't boot from a USB device, edit /usr/share/mkinitrd/mkinitrd_command_generator.sh to comment out lines 453-455
Code:
# If we use any USB module, try to determine the Host Controller
# if echo $MLIST | grep -q "usb"; then
#   MLIST=$(add_usb_hcd)
# fi
Thank you! Unfortunately, my computer did not manage to boot. I get:
Code:
[4.175116][<ffffffff8154fc46>]?rest_init+0x80/0x80
[4.175215]---[end trace 5b6473af4e8e4782]--
 
Old 02-02-2014, 05:36 PM   #6
Bertman123
Member
 
Registered: Jun 2010
Distribution: Slackware
Posts: 204

Rep: Reputation: 28
What steps are you taking to switch to a generic kernel?
 
Old 02-02-2014, 08:20 PM   #7
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,477

Rep: Reputation: 415Reputation: 415Reputation: 415Reputation: 415Reputation: 415
Quote:
Originally Posted by 55020 View Post
I understand from the other thread that you are using mkinitrd_command_generator.sh, not mkinitrd.

Here are two solutions.

(1) If you do not have LVM or LUKS or raid partitions, and you don't boot from a USB device, use mkinitrd - it's not difficult. See the file /boot/README.initrd .

or

(2) If you do have LVM or LUKS or raid partitions, but you don't boot from a USB device, edit /usr/share/mkinitrd/mkinitrd_command_generator.sh to comment out lines 453-455
Code:
# If we use any USB module, try to determine the Host Controller
# if echo $MLIST | grep -q "usb"; then
#   MLIST=$(add_usb_hcd)
# fi
Option #2 would sort of suck if you have a USB keyboard.
 
Old 02-02-2014, 08:29 PM   #8
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,477

Rep: Reputation: 415Reputation: 415Reputation: 415Reputation: 415Reputation: 415
Quote:
Originally Posted by NikolaStanchev View Post
Hi, everyone! I am sorry in advance for my incompetence but i am stuck. I also know the fact that there are similar threads, for which i apologize one more time but i have project to work on and without solving this problem it will be hard to continue. I am running Slackware 14.1; kernel version 3.10.17. I installed it 2 days before and wanted to switch to the generic kernel but after i tried to do this, my system refused to boot the generic kernel. Running mkinitrd - getting this
Code:
ls: cannot access /sys/module/*_hcd/drivers/*: No such file or directory
Please help! Than you very much!
Please boot using the huge kernel (which I assume you are able to do). Then please run the following command...
Code:
$ ls -1 /sys/module/
...and post the results here. Then please run the following command as root...
Code:
$ lsusb -v
...and also post those results here.

There's code in mkinitrd_command_generator.sh that tells me that it should not attempt to find USB controllers unless one of your important boot devices (keyboard or perhaps a disk drive) needs USB to function. You aren't the first one to have had this problem recently.
 
Old 02-03-2014, 03:35 AM   #9
NikolaStanchev
LQ Newbie
 
Registered: Feb 2014
Distribution: Slackware14.1
Posts: 12

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
Please boot using the huge kernel (which I assume you are able to do). Then please run the following command...
Code:
$ ls -1 /sys/module/
...and post the results here. Then please run the following command as root...
Code:
$ lsusb -v
...and also post those results here.

There's code in mkinitrd_command_generator.sh that tells me that it should not attempt to find USB controllers unless one of your important boot devices (keyboard or perhaps a disk drive) needs USB to function. You aren't the first one to have had this problem recently.
I hope it will be helpful.
Attached Files
File Type: txt 1.txt (2.4 KB, 18 views)
File Type: txt 2.txt (31.2 KB, 11 views)
 
Old 02-03-2014, 01:27 PM   #10
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,477

Rep: Reputation: 415Reputation: 415Reputation: 415Reputation: 415Reputation: 415
OK, this is odd.

According to the lsusb output, you have an EHCI host controller on your system. You also don't appear to have a USB keyboard or a USB drive.

Your /sys/module listing also shows an ehci_hcd subdirectory.

I noticed some odd behavior while running some tests. I'm going to open another thread to ask about it (since it has something to do with what you're seeing). OK, there's something odd in my normal user's profile that changes the way my interactive shell works compared to running the same command within a shell script. A brand new user with no special changes to the account works as expected.

Please run the following command while logged in as root:
Code:
for i in $(ls -Ld /sys/module/*_hcd/drivers/*); do  ls -L ${i}; done
If you get something like...
Code:
~$ for i in $(ls -Ld /sys/module/*_hcd/drivers/*); do  ls -L ${i}; done
ls: cannot access /sys/module/ohci_hcd/drivers/pci:ohci_hcd/: No such file or directory
ls: cannot access /sys/module/ohci_hcd/drivers/platform:ohci-platform/: No such file or directory
~$
...then there is something strange in your shell environment.

Last edited by Richard Cranium; 02-03-2014 at 01:45 PM.
 
Old 02-04-2014, 02:44 PM   #11
NikolaStanchev
LQ Newbie
 
Registered: Feb 2014
Distribution: Slackware14.1
Posts: 12

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
OK, this is odd.

According to the lsusb output, you have an EHCI host controller on your system. You also don't appear to have a USB keyboard or a USB drive.

Your /sys/module listing also shows an ehci_hcd subdirectory.

I noticed some odd behavior while running some tests. I'm going to open another thread to ask about it (since it has something to do with what you're seeing). OK, there's something odd in my normal user's profile that changes the way my interactive shell works compared to running the same command within a shell script. A brand new user with no special changes to the account works as expected.

Please run the following command while logged in as root:
Code:
for i in $(ls -Ld /sys/module/*_hcd/drivers/*); do  ls -L ${i}; done
If you get something like...
Code:
~$ for i in $(ls -Ld /sys/module/*_hcd/drivers/*); do  ls -L ${i}; done
ls: cannot access /sys/module/ohci_hcd/drivers/pci:ohci_hcd/: No such file or directory
ls: cannot access /sys/module/ohci_hcd/drivers/platform:ohci-platform/: No such file or directory
~$
...then there is something strange in your shell environment.
Code:
ls: cannot access /sys/module/*_hcd/drivers/*: No such file or directory
 
Old 02-04-2014, 10:38 PM   #12
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,477

Rep: Reputation: 415Reputation: 415Reputation: 415Reputation: 415Reputation: 415
OK, try this:

As root, edit the file /usr/share/mkinitrd/mkinitrd_command_generator.sh and change line 238 from
Code:
for i in $(ls -Ld /sys/module/*_hcd/drivers/*); do
to
Code:
for i in $(/bin/ls -Ld /sys/module/*_hcd/drivers/*); do
and then run the /usr/share/mkinitrd/mkinitrd_command_generator.sh command to see if it works.
 
Old 02-05-2014, 01:15 PM   #13
NikolaStanchev
LQ Newbie
 
Registered: Feb 2014
Distribution: Slackware14.1
Posts: 12

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
OK, try this:

As root, edit the file /usr/share/mkinitrd/mkinitrd_command_generator.sh and change line 238 from
Code:
for i in $(ls -Ld /sys/module/*_hcd/drivers/*); do
to
Code:
for i in $(/bin/ls -Ld /sys/module/*_hcd/drivers/*); do
and then run the /usr/share/mkinitrd/mkinitrd_command_generator.sh command to see if it works.
doesn`t work
 
Old 02-05-2014, 01:40 PM   #14
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 229

Rep: Reputation: 37
Just maybe the permission bits have been screwed up? (like no read access for anyone, including root)
 
Old 02-05-2014, 02:01 PM   #15
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,477

Rep: Reputation: 415Reputation: 415Reputation: 415Reputation: 415Reputation: 415
As root, what do you get when you run...
Code:
for i in $(/bin/ls -Ld /sys/module/*_hcd/drivers/*); do  /bin/ls -L ${i}; done
..?

As root, what does the command...
Code:
alias
...return?

As root, what does the command...
Code:
/bin/ls -Ld /sys/module/ehci_hcd/drivers/*
...return?

I've seen an issue where a user had 'ls' aliased to something stupid, which would break some of the above commands. (That user, by the way, was my normal login user on my main system. I fixed that alias this morning due to this thread.)
 
  


Reply

Tags
boot, ext4, kernel 3.10 initrd, lilo, slackware 14.1


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] switch Huge SMP to Generic czezz Slackware 16 07-07-2011 09:07 AM
[SOLVED] How to switch to the generic kernel Knightron Slackware 9 06-16-2011 05:52 AM
[SOLVED] setting up initrd / generic kernel in Grub2...can't load generic Ubunoob001 Slackware 8 01-05-2011 11:37 PM
how to switch from hugesmp.s to generic.s after intallation markluocanada Slackware 47 06-16-2008 07:41 AM
slack 12, switch to generic kernel from huge kernel, using grub? jaguarrh Slackware 8 09-19-2007 06:29 AM


All times are GMT -5. The time now is 11:02 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