LinuxQuestions.org
Visit Jeremy's Blog.
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 01-01-2014, 10:44 AM   #1
puru
LQ Newbie
 
Registered: Apr 2013
Location: Mumbai
Distribution: Slackware
Posts: 22

Rep: Reputation: Disabled
Post unable to make initrd


I recently upgraded to slackware-14.1. When I run mkinitrd_command_generator.sh i get the following error.

Code:
ls: cannot access /sys/module/*_hcd/drivers/*: No such file or directory
Although an initrd is generated when i run the suggested command, the system fails to boot with the generic kernel. Could anyone help me with it?
 
Old 01-01-2014, 11:28 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,260

Rep: Reputation: Disabled
Looks strange. Please post the command suggested by mkinitrd_command_generator.sh, as well as output of following command, typed as root:
Code:
lspci -k|grep hcd
 
Old 01-01-2014, 12:12 PM   #3
puru
LQ Newbie
 
Registered: Apr 2013
Location: Mumbai
Distribution: Slackware
Posts: 22

Original Poster
Rep: Reputation: Disabled
Thanks for the quick reply. Following is the command suggested by mkinitrd_command_generator.sh

Code:
mkinitrd -c -k 3.10.17-smp -f ext4 -r /dev/sda7 -m usbhid:hid_generic:mbcache:jbd2:ext4 -u -o /boot/initrd.gz
The lspci -k|grep hcd does not return anything.
 
Old 01-01-2014, 12:23 PM   #4
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,260

Rep: Reputation: Disabled
So either that's not a PCI based system, or you have no USB hardware support. Is that right?

This can also happen if you built a custom kernel and didn't include proper drivers, but I guess that's not the case?
 
Old 01-02-2014, 11:48 AM   #5
puru
LQ Newbie
 
Registered: Apr 2013
Location: Mumbai
Distribution: Slackware
Posts: 22

Original Poster
Rep: Reputation: Disabled
Frankly i dont know how to determine whether the system is pci based. But when i run the lspci command in vector linux on this system it shows "Kernel driver in use: ehci_hcd" message.

I have not tried to build a custom kernel.

As for the usb, i can access usb storage from the system. Only one problem with the usb is that i'm unable to make a boot disk using usb.

Do you need any other information that will be helpful to diagnose the problem at hand?

Thanks!
 
Old 01-02-2014, 12:39 PM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,260

Rep: Reputation: Disabled
I don't understand why the lspci -k command don't give the same output on Vector and Slackware.

Could you please, under Slackware, issue following command:
Code:
zcat /proc/config.gz > configSlackware.txt
Also, under Vector, issue following command:
Code:
zcat /proc/config.gz > configVector.txt
then attach both files configSlackware.txt and configVector.txt to your next post.

Also, please give output of following commands under Slackware:
Code:
ls -l /lib/modules
uname -a

Last edited by Didier Spaier; 01-02-2014 at 12:41 PM.
 
Old 01-03-2014, 01:32 PM   #7
puru
LQ Newbie
 
Registered: Apr 2013
Location: Mumbai
Distribution: Slackware
Posts: 22

Original Poster
Rep: Reputation: Disabled
The output of ls -l /lib/modules is as follows:
Code:
total 8
drwxr-xr-x 3 root root 4096 Dec 28 20:26 3.10.17
drwxr-xr-x 3 root root 4096 Dec 28 20:26 3.10.17-smp
The output of uname -a is as follows:

Code:
Linux darkstar 3.10.17-smp #2 SMP Wed Oct 23 17:13:14 CDT 2013 i686 Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz GenuineIntel GNU/Linux
Also attached the outputs of zcat /proc/config.gz in both Slackware and Vector Linux.
Attached Files
File Type: txt configSlackware.txt (138.5 KB, 11 views)
File Type: txt configVector.txt (119.9 KB, 9 views)
 
Old 01-03-2014, 02:09 PM   #8
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,260

Rep: Reputation: Disabled
Sorry, no clue. I just saw that the 'huge" kernel of Slackware 14.1 has the ehci_hcd driver configured as a module, that is not the case in Slackware 14.0 in which this driver is built in the kernel.

But I don't know if that can cause a problem when building the initrd. Still, I hardly understand why "lspci -k" doesn't list this driver. Would you be kind enough to plug in some USB device under Slackware, then type
Code:
lsmod > lsmod.txt
and attach that file to your next post?

In any case, I'd suggest you stay with the huge kernel till someone finds a more helpful answer, this usually doesn't hurt (unless in some special cases like conflicting drivers loaded, for instance).

Just one more question: does your USB devices work properly when using the huge Slackware kernel ?

Last edited by Didier Spaier; 01-03-2014 at 02:55 PM.
 
Old 01-03-2014, 03:39 PM   #9
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 906

Rep: Reputation: 154Reputation: 154
I would also suggest running this command as root -

Code:
dmesg | grep ehci
Alex
 
Old 01-04-2014, 01:44 PM   #10
puru
LQ Newbie
 
Registered: Apr 2013
Location: Mumbai
Distribution: Slackware
Posts: 22

Original Poster
Rep: Reputation: Disabled
Please find attached the output of the lsmod after usb is attached.

I can read from and write to the usb. Lately i was unable to make a bootstick though. Also, the video of the game speed-dreams 2 is not displayed properly.
Attached Files
File Type: txt lsmod.txt (3.3 KB, 22 views)
 
Old 01-04-2014, 02:03 PM   #11
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,260

Rep: Reputation: Disabled
So, modules ehci_pci and ehci_hcd are loaded. I don't know why no module shows in lspci -k output.
 
Old 01-18-2014, 03:19 AM   #12
lems
Member
 
Registered: May 2004
Distribution: BSD
Posts: 269

Rep: Reputation: 119Reputation: 119
Hello,

I get
Code:
ls: cannot access /sys/module/*_hcd/drivers/*: No such file or directory
when running mkinitrd_command_generator.sh on a 3.12.7 kernel on Slackware -current, built using testing/source/config-testing-3.12/config-generic-smp-3.12-smp. I only made sure that CONFIG_X86_PAE, CONFIG_PREEMPT, CONFIG_SCHED_AUTOGROUP and Processor type are enabled/correct (I also disabled CONFIG_DEBUG_KERNEL, as I use the nvidia driver). Otherwise I didn't change anything.

When running the same command on a 3.10.17 kernel (huge or generic), I don't get this message. The 3.12.8-generic-smp kernel boots, though. I am able to use USB devices etc. Is this something I should worry about? Or can I ignore this?

lems

Last edited by lems; 01-18-2014 at 03:32 AM.
 
Old 01-18-2014, 04:11 AM   #13
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,260

Rep: Reputation: Disabled
It *could* be that paths have changed in tree /sys.

Try this:
Code:
find /sys -name "*pci:?hci_hcd*"
and please post the output (both kernels).

Last edited by Didier Spaier; 01-18-2014 at 04:12 AM.
 
Old 01-18-2014, 05:23 AM   #14
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 2,325

Rep: Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928
How about
Code:
ls /sys/module/ehci_pci/drivers/*
Maybe this would work:

Code:
mkinitrd -c -k 3.10.17-smp -f ext4 -r /dev/sda7 -m usb-storage:ehci-hcd:ehci-pci:usbhid:hid_generic:mbcache:jbd2:ext4 -u -o /boot/initrd.gz
 
Old 01-18-2014, 09:33 AM   #15
lems
Member
 
Registered: May 2004
Distribution: BSD
Posts: 269

Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by Didier Spaier View Post
It *could* be that paths have changed in tree /sys.

Try this:
Code:
find /sys -name "*pci:?hci_hcd*"
and please post the output (both kernels).
Hi,

thanks for the quick reply.

find /sys -name "*pci:?hci_hcd*" on 3.10.17-smp (huge):
Code:
/sys/module/ohci_hcd/drivers/pci:ohci_hcd
On 3.12.8-generic-smp, I get no ouput.

edit:

ls /sys/module/ehci_pci/drivers/* gives this on 3.12.8:
Code:
/sys/module/ehci_pci/drivers/pci:ehci-pci@

Last edited by lems; 01-18-2014 at 09:35 AM.
 
  


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
cannot make InitRd smeezekitty Linux - Newbie 3 10-07-2009 03:49 PM
how to make initrd? samwise17 Slackware - Installation 12 09-16-2007 09:04 AM
Is it necessary to make the initrd? jacobselvin Linux - Kernel 3 08-19-2006 09:03 AM
make initrd error imagineaxion Debian 4 02-08-2005 10:29 AM
initrd how to make one? watashiwaotaku7 Linux - General 18 03-20-2004 12:53 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:54 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration