Cannot boot to compiled kernel

Cannot boot to compiled kernel

[Daniel Bokser]

Hi Everyone,

I know this is probably the newbiest of questions, but I am trying to compile and boot off of the kernel.  
I am running Arch Linux and I am following this guide: https://wiki.archlinux.org/index.php/Kernels/Traditional_compilation

Despite using "linux480" below (I tried this a few weeks ago), the kernel version I am using is
Linux 4.9.0-rc3 "Psychotic Stoned Sheep" (I love these names). I use systemd-boot as a boot loader.

1) Pulled down kernel from git
2) Ran make localmodconfig
3) Ran make menuconfig and changed the local version to a custom string
4) Ran make 
5) Ran sudo make modules_install
6) Ran sudo cp arch/x86_64/bzImage /boot/vmlinuz-linux480
7) Added /etc/mkinitcpio.d/linux480.preset,
    which is similar to linux.preset except with linux480 names
8) Ran mkinitcpio -p linux480
9) Ran sudo cp System.map /boot/System.map-linux480
10) Added entry file to /boot/entries called linux480 and used the current entry as a template
11) Rebooted and selected linux480

Now I am thrown into the recovery shell with an 'Unable to find root device /dev/sdc2' (my SSD).
The real strange thing is that the (PS/2) keyboard doesn't work, so I can't even run commands.
Tried also USB keyboard to no avail.
I also have a bunch of "Unknown symbol" errors from scsi_mod which fill most of the screen. 

I'm thinking the RAM disk is bad, but not sure. No amount of Google-fu was able to help me out with this one. 

Any help would be appreciated.  Thank you!

-Daniel

Cannot boot to compiled kernel

[Quentin Lambert]

Hi,
On 11/02/2016 12:05 PM, Daniel Bokser wrote:
> Now I am thrown into the recovery shell with an 'Unable to find root device /dev/sdc2' (my SSD).
> The real strange thing is that the (PS/2) keyboard doesn't work, so I can't even run commands.
> Tried also USB keyboard to no avail.
> I also have a bunch of "Unknown symbol" errors from scsi_mod which fill most of the screen.
>
> I'm thinking the RAM disk is bad, but not sure. No amount of Google-fu was able to help me out with this one.
>
I had a similar problem, check to see if the RAM is ok but the problem
might be due to something else.

I was able to make it work thanks to this e-mail:

https://lkml.org/lkml/2016/10/19/271


I changed to

CONFIG_MODVERSIONS=n

But naively applying the patches mentioned in the e-mail did not work for me
and I haven't had the time to look further into the problem and give 
relevant
feedback to the thread.

Quentin

Cannot boot to compiled kernel

[Daniel.]

2016-11-02 9:27 GMT-02:00 Quentin Lambert <lambert.quentin@gmail.com>:

> Hi,
> On 11/02/2016 12:05 PM, Daniel Bokser wrote:
> > Now I am thrown into the recovery shell with an 'Unable to find root
> device /dev/sdc2' (my SSD).
> > The real strange thing is that the (PS/2) keyboard doesn't work, so I
> can't even run commands.
> > Tried also USB keyboard to no avail.
> > I also have a bunch of "Unknown symbol" errors from scsi_mod which fill
> most of the screen.
> >
> > I'm thinking the RAM disk is bad, but not sure. No amount of Google-fu
> was able to help me out with this one.
> >
> I had a similar problem, check to see if the RAM is ok but the problem
> might be due to something else.
>
> I was able to make it work thanks to this e-mail:
>
> https://lkml.org/lkml/2016/10/19/271
>
>
> I changed to
>
> CONFIG_MODVERSIONS=n
>
> But naively applying the patches mentioned in the e-mail did not work for
> me
> and I haven't had the time to look further into the problem and give
> relevant
> feedback to the thread.
>
> Quentin
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>


I would suggest you to compile ssd and ps2 keyboard drivers built in, so
even if some goes wrong on initrd you may still mount rootfs and have
keyboard working. The "Unknown symbol" may mean that something was wrong in
kernel compilation.

Regards,
-- 
*"Do or do not. There is no try"*
  *Yoda Master*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161103/a4baf1b9/attachment.html 

Cannot boot to compiled kernel

[Matias Mucciolo]

On Thursday 03 November 2016 00:56:21 Daniel. wrote:
> 2016-11-02 9:27 GMT-02:00 Quentin Lambert <lambert.quentin@gmail.com>:
> 
> > Hi,
> > On 11/02/2016 12:05 PM, Daniel Bokser wrote:
> > > Now I am thrown into the recovery shell with an 'Unable to find root
> > device /dev/sdc2' (my SSD).
> > > The real strange thing is that the (PS/2) keyboard doesn't work, so I
> > can't even run commands.
> > > Tried also USB keyboard to no avail.
> > > I also have a bunch of "Unknown symbol" errors from scsi_mod which fill
> > most of the screen.
> > >
> > > I'm thinking the RAM disk is bad, but not sure. No amount of Google-fu
> > was able to help me out with this one.
> > >
> > I had a similar problem, check to see if the RAM is ok but the problem
> > might be due to something else.
> >
> > I was able to make it work thanks to this e-mail:
> >
> > https://lkml.org/lkml/2016/10/19/271
> >
> >
> > I changed to
> >
> > CONFIG_MODVERSIONS=n
> >
> > But naively applying the patches mentioned in the e-mail did not work for
> > me
> > and I haven't had the time to look further into the problem and give
> > relevant
> > feedback to the thread.
> >
> > Quentin
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
> 
> 
> I would suggest you to compile ssd and ps2 keyboard drivers built in, so
> even if some goes wrong on initrd you may still mount rootfs and have
> keyboard working. The "Unknown symbol" may mean that something was wrong in
> kernel compilation.
> 
> Regards,
> -- 
> *"Do or do not. There is no try"*
>   *Yoda Master*


also the module for the filesystem you use in root part.

Matias

Cannot boot to compiled kernel

[Daniel Bokser]

> On Nov 3, 2016, at 11:22 AM, Matias Mucciolo <mmucciolo@suteba.org.ar> wrote:
> 
> 
> 
> On Thursday 03 November 2016 00:56:21 Daniel. wrote:
>> 2016-11-02 9:27 GMT-02:00 Quentin Lambert <lambert.quentin@gmail.com>:
>> 
>>> Hi,
>>> On 11/02/2016 12:05 PM, Daniel Bokser wrote:
>>>> Now I am thrown into the recovery shell with an 'Unable to find root
>>> device /dev/sdc2' (my SSD).
>>>> The real strange thing is that the (PS/2) keyboard doesn't work, so I
>>> can't even run commands.
>>>> Tried also USB keyboard to no avail.
>>>> I also have a bunch of "Unknown symbol" errors from scsi_mod which fill
>>> most of the screen.
>>>> 
>>>> I'm thinking the RAM disk is bad, but not sure. No amount of Google-fu
>>> was able to help me out with this one.
>>>> 
>>> I had a similar problem, check to see if the RAM is ok but the problem
>>> might be due to something else.
>>> 
>>> I was able to make it work thanks to this e-mail:
>>> 
>>> https://lkml.org/lkml/2016/10/19/271
>>> 
>>> 
>>> I changed to
>>> 
>>> CONFIG_MODVERSIONS=n
>>> 
>>> But naively applying the patches mentioned in the e-mail did not work for
>>> me
>>> and I haven't had the time to look further into the problem and give
>>> relevant
>>> feedback to the thread.
>>> 
>>> Quentin
>>> 
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>> 
>> 
>> 
>> I would suggest you to compile ssd and ps2 keyboard drivers built in, so
>> even if some goes wrong on initrd you may still mount rootfs and have
>> keyboard working. The "Unknown symbol" may mean that something was wrong in
>> kernel compilation.
>> 
>> Regards,
>> -- 
>> *"Do or do not. There is no try"*
>>  *Yoda Master*
> 
> 
> also the module for the filesystem you use in root part.
> 
> Matias
> 
> 

Thanks everyone!  So I compiled keyboard, SATA, and BTRFS drivers in and was able to get further, but it looks like it had trouble starting up LXDE (it was repeatedly starting and stopping LXDE).  Booting up in single user mode, I was able to get a prompt.  I attempted startx but it failed.  I looked and it looked like it was attempting to use the Nvidia modules, but they weren?t in the /lib/modules/4.9.0? directory (I have an Nvidia 670).  It looks like they are stored as extra modules in the extramodules softlink in my default installation (now kernel 4.8).  

So I am gathering that many of the modules used in my default installation are not making it over to 4.9.  When running make localmodconfig, I am noticing error messages related to Nvidia and virtual box.  Some examples:

Nvidia config not found!!
Vbox_pci config not found!!

I also did a diff on the modules.symbols files between 4.9 and the default kernel and noticed many missing symbols in the 4.9 modules.symbols.  So I feel I?m missing a step somewhere.  Isn?t it supposed to make sure all loaded and unloaded modules are copied to 4.9?

Thanks!

-Daniel

Cannot boot to compiled kernel

[Greg KH]

On Mon, Nov 07, 2016 at 11:26:50PM -0500, Daniel Bokser wrote:
> So I am gathering that many of the modules used in my default installation are not making it over to 4.9.  When running make localmodconfig, I am noticing error messages related to Nvidia and virtual box.  Some examples:
> 
> Nvidia config not found!!
> Vbox_pci config not found!!

Those kernel modules are not included in the kernel.org release, so you
are going to have to install them yourself.

good luck!

greg k-h

Cannot boot to compiled kernel

[Andrey Skvortsov]

On 16-11-07 23:26, Daniel Bokser wrote:
> 
> > On Nov 3, 2016, at 11:22 AM, Matias Mucciolo <mmucciolo@suteba.org.ar> wrote:
> > 
> > 
> 
> Thanks everyone!  So I compiled keyboard, SATA, and BTRFS drivers in and was able to get further, but it looks like it had trouble starting up LXDE (it was repeatedly starting and stopping LXDE).  Booting up in single user mode, I was able to get a prompt.  I attempted startx but it failed.  I looked and it looked like it was attempting to use the Nvidia modules, but they weren?t in the /lib/modules/4.9.0? directory (I have an Nvidia 670).  It looks like they are stored as extra modules in the extramodules softlink in my default installation (now kernel 4.8).  
> 
> So I am gathering that many of the modules used in my default installation are not making it over to 4.9.  When running make localmodconfig, I am noticing error messages related to Nvidia and virtual box.  Some examples:
> 
> Nvidia config not found!!

You have used proprietary driver from Nvidia. It is not included in
the kernel. I think this is the reason for your problem with LXDE.

The best way would be to use open source driver that is supported by
the mainline kernel - nouveau (config option DRM_NOUVEAU).
According to the nouveau site [1], your chip is supported. Try it.

1. https://nouveau.freedesktop.org/wiki/FeatureMatrix/ 

-- 
Best regards,
Andrey Skvortsov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161108/5ec27592/attachment.bin 

Cannot boot to compiled kernel

[Daniel Bokser]

> On Nov 8, 2016, at 5:50 AM, Andrey Skvortsov <andrej.skvortzov@gmail.com> wrote:
> 
> On 16-11-07 23:26, Daniel Bokser wrote:
>> 
>>> On Nov 3, 2016, at 11:22 AM, Matias Mucciolo <mmucciolo@suteba.org.ar> wrote:
>>> 
>>> 
>> 
>> Thanks everyone!  So I compiled keyboard, SATA, and BTRFS drivers in and was able to get further, but it looks like it had trouble starting up LXDE (it was repeatedly starting and stopping LXDE).  Booting up in single user mode, I was able to get a prompt.  I attempted startx but it failed.  I looked and it looked like it was attempting to use the Nvidia modules, but they weren?t in the /lib/modules/4.9.0? directory (I have an Nvidia 670).  It looks like they are stored as extra modules in the extramodules softlink in my default installation (now kernel 4.8).  
>> 
>> So I am gathering that many of the modules used in my default installation are not making it over to 4.9.  When running make localmodconfig, I am noticing error messages related to Nvidia and virtual box.  Some examples:
>> 
>> Nvidia config not found!!
> 
> You have used proprietary driver from Nvidia. It is not included in
> the kernel. I think this is the reason for your problem with LXDE.
> 
> The best way would be to use open source driver that is supported by
> the mainline kernel - nouveau (config option DRM_NOUVEAU).
> According to the nouveau site [1], your chip is supported. Try it.
> 
> 1. https://nouveau.freedesktop.org/wiki/FeatureMatrix/ 
> 
> -- 
> Best regards,
> Andrey Skvortsov

Thanks!  I tried to use nouveau.  It seems that the kernel cannot load any dynamically linked module, including nouveau.  I am kicked to the emergency console (after statically linking all the necessary drivers to ready my SSD). When I do a modprobe nouveau, I get a bunch of Unknown symbol errors similar to the errors I stated in my previous email. It errors out stating ERROR: could not insert nouveau: Invalid argument

Some examples include:

drm: no known symbol version for memcpy
drm: Unknown symbol memcpy (err -22)
drm: no known symbol version for __put_user_4
drm: Unknown symbol __put_user_4 (err -22)

It seems there is an underlying problem with loading the dynamically linked modules.  lsmod reveals exactly 2 modules: crc16 and hid_generic.  Honestly I am surprised there are any modules here.  

As was stated before, there might have been a problem compiling these modules.  Has anyone encountered this issue before?

Thanks!

-Daniel

Cannot boot to compiled kernel

[Daniel.]

2016-11-10 2:48 GMT-02:00 Daniel Bokser <dan.bokser@gmail.com>:
>
>> On Nov 8, 2016, at 5:50 AM, Andrey Skvortsov <andrej.skvortzov@gmail.com> wrote:
>>
>> On 16-11-07 23:26, Daniel Bokser wrote:
>>>
>>>> On Nov 3, 2016, at 11:22 AM, Matias Mucciolo <mmucciolo@suteba.org.ar> wrote:
>>>>
>>>>
>>>
>>> Thanks everyone!  So I compiled keyboard, SATA, and BTRFS drivers in and was able to get further, but it looks like it had trouble starting up LXDE (it was repeatedly starting and stopping LXDE).  Booting up in single user mode, I was able to get a prompt.  I attempted startx but it failed.  I looked and it looked like it was attempting to use the Nvidia modules, but they weren?t in the /lib/modules/4.9.0? directory (I have an Nvidia 670).  It looks like they are stored as extra modules in the extramodules softlink in my default installation (now kernel 4.8).
>>>
>>> So I am gathering that many of the modules used in my default installation are not making it over to 4.9.  When running make localmodconfig, I am noticing error messages related to Nvidia and virtual box.  Some examples:
>>>
>>> Nvidia config not found!!
>>
>> You have used proprietary driver from Nvidia. It is not included in
>> the kernel. I think this is the reason for your problem with LXDE.
>>
>> The best way would be to use open source driver that is supported by
>> the mainline kernel - nouveau (config option DRM_NOUVEAU).
>> According to the nouveau site [1], your chip is supported. Try it.
>>
>> 1. https://nouveau.freedesktop.org/wiki/FeatureMatrix/
>>
>> --
>> Best regards,
>> Andrey Skvortsov
>
> Thanks!  I tried to use nouveau.  It seems that the kernel cannot load any dynamically linked module, including nouveau.  I am kicked to the emergency console (after statically linking all the necessary drivers to ready my SSD). When I do a modprobe nouveau, I get a bunch of Unknown symbol errors similar to the errors I stated in my previous email. It errors out stating ERROR: could not insert nouveau: Invalid argument
>
> Some examples include:
>
> drm: no known symbol version for memcpy
> drm: Unknown symbol memcpy (err -22)
> drm: no known symbol version for __put_user_4
> drm: Unknown symbol __put_user_4 (err -22)
>
> It seems there is an underlying problem with loading the dynamically linked modules.  lsmod reveals exactly 2 modules: crc16 and hid_generic.  Honestly I am surprised there are any modules here.
>
> As was stated before, there might have been a problem compiling these modules.  Has anyone encountered this issue before?
>
> Thanks!
>
> -Daniel

Usually this means that the modules you're trying to load wasn't
compiled to the running kernel. But it may be another problem. If you
have /proc/config.gz you may check if the CONFIG_* options that you
selected are really there, with something like `zcat /proc/config.gz |
grep CONFIG_SOME_OPTION'.

Regards,

-- 
"Do or do not. There is no try"
  Yoda Master