LinuxQuestions.org
Help answer threads with 0 replies.
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 11-17-2014, 05:21 AM   #1
lems
Member
 
Registered: May 2004
Distribution: BSD
Posts: 269

Rep: Reputation: 119Reputation: 119
mkinitrd_command_generator.sh: broken with 3.17.3 kernel


Hello,

today I've compiled a 3.17.3 kernel with the newly added generic config in -current.

What I noticed was that it did not find the modules directory, complaining that on line 417 a binary operator was expected or so.

This command:
Code:
strings /boot/vmlinuz-huge-3.14.24 | grep '(.*@.*) #'
creates the following output:
Code:
3.14.24 (root@hive64) #2 SMP Fri Nov 14 13:08:43 CST 2014
But this is what happens with my shiny new generic kernel (I only changed a few options like enabling PREEMPT and CONFIG_SCHED_AUTOGROUP):
Code:
3.17.3 (root@aristipp) #1 SMP PREEMPT Mon Nov 17 11:37:31 CET 2014
3.17.3 (root@aristipp) (gcc version 4.8.3 (GCC) ) #1 SMP PREEMPT Mon Nov 17 11:37:31 CET 2014
So the command
Code:
strings /boot/vmlinuz-generic-3.17.3 | grep '(.*@.*) #' | cut -f1 -d' '
will output 3.17.3 two times. I added a `sed 1q' and the script worked like it should. No idea if this is a local problem, thought I'd inform someone about this.

Last edited by lems; 11-17-2014 at 05:23 AM.
 
Old 11-17-2014, 05:45 AM   #2
Nh3xus
Member
 
Registered: Jan 2013
Location: France
Distribution: Slackware 14.1 32 bits
Posts: 211

Rep: Reputation: 56
Hi,

I've done the same kernel building as you for my brand new laptop.

Except that I've used the .config that Pat made for the huge kernel. (Yeah, I know... but it works)

Perhaps appending a custom string to the kernel name would have prevented mkinitrd_command_generator.sh to fail.

Also, if you don't use some specific configuration like LUKS and/or LVM on your /boot and /root partitions, then you can use the mkinird command manually.

Here the command I've used : mkinitrd -c -k 3.17.3 -m ext4

That's my first kernel compile so far.

I had to do it in order to have the following recognized :

- Proper Pstate CPU governor driver for my Haswell CPU
- Recognition of my ALPS touchpad
- Recognition of my Logitech Unifying dongle

Last edited by Nh3xus; 11-17-2014 at 05:49 AM.
 
Old 11-17-2014, 07:11 AM   #3
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,838

Rep: Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113
If you use huge config, then you don't need initrd anymore
 
Old 11-17-2014, 08:02 AM   #4
xflow7
Member
 
Registered: May 2004
Distribution: Slackware
Posts: 214

Rep: Reputation: 45
Is that strictly true? I seem to recall that when I've used huge in the past I still needed an initrd if I used LVM. Maybe that's no longer the case, but I'm pretty sure it was as of 13 or so.
 
Old 11-17-2014, 09:58 AM   #5
lems
Member
 
Registered: May 2004
Distribution: BSD
Posts: 269

Original Poster
Rep: Reputation: 119Reputation: 119
It seemed to be a problem just on my machine, at least the 32 bit kernel I compiled on my T60 (generic-smp 3.17.3) didn't have this problem. As for the example (kernel huge): I don't have kernel-generic installed, instead I always build a newer generic and leave kernel-huge installed just in case. However, I use UUIDs with lilo, and I couldn't boot the huge kernel without an initrd.
 
Old 11-17-2014, 01:24 PM   #6
mostlyharmless
Senior Member
 
Registered: Jan 2008
Distribution: Arch/Slackware/Knoppix
Posts: 1,789
Blog Entries: 14

Rep: Reputation: 279Reputation: 279Reputation: 279
Quote:
Also, if you don't use some specific configuration like LUKS and/or LVM on your /boot and /root partitions, then you can use the mkinird command manually.
You can always use it manually. If you don't like typing in something really long, just write it to a file and execute it with sh. I have found the script is a bit hit and miss anyway.
 
  


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
mkinitrd_command_generator and ehci_hcd pdi Slackware 3 11-07-2014 11:14 AM
mkinitrd_command_generator.sh doesn't recognize kernel file ...? chexmix Slackware 13 06-17-2013 06:08 AM
Boot error message (mkinitrd_command_generator.sh) samac Slackware 12 03-05-2010 01:27 PM
Broken kernel in FC5 Phyrkrakr Fedora 3 09-18-2006 11:24 PM
cdrecord broken in kernel 2.6? vharishankar Slackware 9 08-05-2006 11:47 AM

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

All times are GMT -5. The time now is 01:13 PM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration