Re: Segmentation faults with aptitude and apt-get on some packages

[rod]

I kinda figured that.  I was trying to be clear in case someone else was
following along.  My question still is, is it necessary to run
"update-initramfs -c -k 4.8.11" if "make install" performs that
function? Does make install do the same thing as the update-initramfs
command or do they do something different.

Either way running "make install" and pointing
image=/boot/vmlinuz-4.8.11 works.  It now boots and uname-r returns 4.8.11.

Now to see if it has eliminated the segfault I got when trying to access
webmin (don't know if it's localized to webmin but it's what I was
working on when this came up.

Thanks for the help.

Rod

On 12/2/2016 1:00 PM, John Paul Adrian Glaubitz wrote:
> You don't need to go through all steps again. Just "make install" is enough. 
> Unless you call "make clean", the compiled files and kernel are still in the 
> kernel's source directory.
> 
> Adrian
> 
>> On Dec 2, 2016, at 7:45 PM, rod  wrote:
>>
>>> On 12/2/2016 12:13 PM, John Paul Adrian Glaubitz wrote:
>>> Did you run "make install" in the kernel's source directory after building 
>>> kernel or did I forget mentioning it?
>>>
>>> Adrian
>>>
>>> PS: Sorry for the bad quoting style. Currently on mobile.
>>>
> On Dec 2, 2016, at 7:05 PM, rod  wrote:
>
> On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote:
> Change the first SILO entry to:
>
> image=/boot/vmlinuz-4.8.11
>  label=Linux
>  initrd=/boot/initrd.img-4.8.11
>
> You simply forgot to modify silo.conf to point to the correct kernel and 
> initrd.
>
> Currently it's configured to boot "vmlinuz" from the system's root 
> directory which is most likely a symlink to a kernel in /boot (check "ls 
> -l /vmlinuz") and use /initrd-4.8.11 as the initrd which is probably a 
> symlink as well.
>
> Adrian
>
>> On Dec 2, 2016, at 6:32 PM, rod  wrote:
>>
>> image=/vmlinuz
>>  label=Linux
>>  initrd=/initrd.img-4.8.11


 I noticed that whilst typing the email and have gone looking for
 vmlinuz-4.8.11.

 It's not in /boot and updatedb/locate doesn't show one on the system
 symlinked or otherwise.

 Did we not create it somehow? Is it supposed to be created when the
 kernel is built?

 Building kernels is fun! ;)
>>>
>> I did make "modules_install" but not "make install".
>>
>> $ cd linux-4.8.11
>> $ cp -av /boot/config-$(uname -r) .
>> $ make oldconfig (Just always  until the prompt comes back)
>> $ make && make modules_install
>> $ update-initramfs -c -k 4.8.11
>>
>> If I run "make install" it appears to run update-initramfs
>> automatically. So is the last line not needed?
>>
>> Personally I'd rather top reply. I find it easier to see new comments
>> that way.  No big deal either way.
>>
>> Rod
> 

Re: Segmentation faults with aptitude and apt-get on some packages

[rod]

On 12/2/2016 12:13 PM, John Paul Adrian Glaubitz wrote:
> Did you run "make install" in the kernel's source directory after building 
> kernel or did I forget mentioning it?
> 
> Adrian
> 
> PS: Sorry for the bad quoting style. Currently on mobile.
> 
>> On Dec 2, 2016, at 7:05 PM, rod  wrote:
>>
>>> On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote:
>>> Change the first SILO entry to:
>>>
>>> image=/boot/vmlinuz-4.8.11
>>>   label=Linux
>>>   initrd=/boot/initrd.img-4.8.11
>>>
>>> You simply forgot to modify silo.conf to point to the correct kernel and 
>>> initrd.
>>>
>>> Currently it's configured to boot "vmlinuz" from the system's root 
>>> directory which is most likely a symlink to a kernel in /boot (check "ls -l 
>>> /vmlinuz") and use /initrd-4.8.11 as the initrd which is probably a symlink 
>>> as well.
>>>
>>> Adrian
>>>
 On Dec 2, 2016, at 6:32 PM, rod  wrote:

 image=/vmlinuz
   label=Linux
   initrd=/initrd.img-4.8.11
>>
>>
>> I noticed that whilst typing the email and have gone looking for
>> vmlinuz-4.8.11.
>>
>> It's not in /boot and updatedb/locate doesn't show one on the system
>> symlinked or otherwise.
>>
>> Did we not create it somehow? Is it supposed to be created when the
>> kernel is built?
>>
>> Building kernels is fun! ;)
> 
I did make "modules_install" but not "make install".

$ cd linux-4.8.11
$ cp -av /boot/config-$(uname -r) .
$ make oldconfig (Just always  until the prompt comes back)
$ make && make modules_install
$ update-initramfs -c -k 4.8.11

If I run "make install" it appears to run update-initramfs
automatically. So is the last line not needed?

Personally I'd rather top reply. I find it easier to see new comments
that way.  No big deal either way.

Rod

Re: Segmentation faults with aptitude and apt-get on some packages

[John Paul Adrian Glaubitz]

Did you run "make install" in the kernel's source directory after building 
kernel or did I forget mentioning it?

Adrian

PS: Sorry for the bad quoting style. Currently on mobile.

> On Dec 2, 2016, at 7:05 PM, rod  wrote:
> 
>> On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote:
>> Change the first SILO entry to:
>> 
>> image=/boot/vmlinuz-4.8.11
>>   label=Linux
>>   initrd=/boot/initrd.img-4.8.11
>> 
>> You simply forgot to modify silo.conf to point to the correct kernel and 
>> initrd.
>> 
>> Currently it's configured to boot "vmlinuz" from the system's root directory 
>> which is most likely a symlink to a kernel in /boot (check "ls -l /vmlinuz") 
>> and use /initrd-4.8.11 as the initrd which is probably a symlink as well.
>> 
>> Adrian
>> 
>>> On Dec 2, 2016, at 6:32 PM, rod  wrote:
>>> 
>>> image=/vmlinuz
>>>   label=Linux
>>>   initrd=/initrd.img-4.8.11
> 
> 
> I noticed that whilst typing the email and have gone looking for
> vmlinuz-4.8.11.
> 
> It's not in /boot and updatedb/locate doesn't show one on the system
> symlinked or otherwise.
> 
> Did we not create it somehow? Is it supposed to be created when the
> kernel is built?
> 
> Building kernels is fun! ;)

Re: Segmentation faults with aptitude and apt-get on some packages

[rod]

On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote:
> Change the first SILO entry to:
> 
> image=/boot/vmlinuz-4.8.11
>label=Linux
>initrd=/boot/initrd.img-4.8.11
> 
> You simply forgot to modify silo.conf to point to the correct kernel and 
> initrd.
> 
> Currently it's configured to boot "vmlinuz" from the system's root directory 
> which is most likely a symlink to a kernel in /boot (check "ls -l /vmlinuz") 
> and use /initrd-4.8.11 as the initrd which is probably a symlink as well.
> 
> Adrian
> 
>> On Dec 2, 2016, at 6:32 PM, rod  wrote:
>>
>> image=/vmlinuz
>>label=Linux
>>initrd=/initrd.img-4.8.11


I noticed that whilst typing the email and have gone looking for
vmlinuz-4.8.11.

It's not in /boot and updatedb/locate doesn't show one on the system
symlinked or otherwise.

Did we not create it somehow? Is it supposed to be created when the
kernel is built?

Building kernels is fun! ;)

Re: Segmentation faults with aptitude and apt-get on some packages

[John Paul Adrian Glaubitz]

Change the first SILO entry to:

image=/boot/vmlinuz-4.8.11
   label=Linux
   initrd=/boot/initrd.img-4.8.11

You simply forgot to modify silo.conf to point to the correct kernel and initrd.

Currently it's configured to boot "vmlinuz" from the system's root directory 
which is most likely a symlink to a kernel in /boot (check "ls -l /vmlinuz") 
and use /initrd-4.8.11 as the initrd which is probably a symlink as well.

Adrian

> On Dec 2, 2016, at 6:32 PM, rod  wrote:
> 
> image=/vmlinuz
>label=Linux
>initrd=/initrd.img-4.8.11

Re: Segmentation faults with aptitude and apt-get on some packages

[rod]

On 12/2/2016 9:50 AM, John Paul Adrian Glaubitz wrote:
> On 12/02/2016 04:35 PM, rod wrote:
>> [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 4.22.33 2007/06/18 12:45'
>> [0.00] PROMLIB: Root node compatible:
>> [0.00] Linux version 4.8.0-1-sparc64-smp
>> (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian
>> 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13)
> 
> This does not look like a kernel that you built yourself. Note the date
> when it was built and which compiler was used. If you had built it
> directly from source and without going through any Debian-specific
> steps, the kernel version would not include "Debian" and would be
> built with gcc-6. Also, the date would be around the past days.
> 
>> Gave up waiting for root device.  Common problems:
>>  - Boot args (cat /proc/cmdline)
>>- Check rootdelay= (did the system wait long enough?)
>>- Check root= (did the system wait for the right device?)
>>  - Missing modules (cat /proc/modules; ls /dev)
>> ALERT!  /dev/sda4 does not exist.  Dropping to a shell!
> 
> It's missing the drivers for your disk controllers. Are you sure
> you built the initrd properly and that the SILO entry for "Linux"
> points to the correct kernel and initrd?
> 
> Adrian
> 
I'm not sure about anything when it comes to this. Mostly it's new. I
follow directions and read about what I don't understand so I CAN
understand whats going on.

I built the kernel following these directions (with Anatoly's
modification of 'make olddefconfig' because I was being lazy in not
wanting to hit ENTER alot.  That may be my mistake and I will go back
and try it with 'make oldconfig' just to be sure...):

$ apt update
$ apt-get build-dep linux
$ cd /usr/src/
$ wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.11.tar.xz
$ tar xf linux-4.8.11.tar.xz
$ cd linux-4.8.11
$ cp -av /boot/config-$(uname -r)
$ make oldconfig (Just always  until the prompt comes back)
$ make && make modules_install
$ update-initramfs -c -k 4.8.11

The build went fine (as near as I can tell) and the tail end of the
output is below:
  INSTALL /lib/firmware/edgeport/down2.fw
  INSTALL /lib/firmware/edgeport/down3.bin
  INSTALL /lib/firmware/whiteheat_loader.fw
  INSTALL /lib/firmware/whiteheat.fw
  INSTALL /lib/firmware/keyspan_pda/keyspan_pda.fw
  INSTALL /lib/firmware/keyspan_pda/xircom_pgs.fw
  INSTALL /lib/firmware/cpia2/stv0672_vp4.bin
  DEPMOD  4.8.11

root@mw-monitor:/usr/src/linux-4.8.11# update-initramfs -c -k 4.8.11
update-initramfs: Generating /boot/initrd.img-4.8.11
cp: cannot stat '/etc/modprobe.d/*': No such file or directory

root@mw-monitor:/usr/src/linux-4.8.11# nano /etc/silo.conf

silo.conf now looks like this:

root=/dev/sda4
partition=1
default=Linux
read-only
timeout=100

image=/vmlinuz
label=Linux
initrd=/initrd.img-4.8.11

image=/vmlinuz
label=LinuxWORKING
initrd=/initrd.img

image=/vmlinuz.old
label=LinuxOLD
initrd=/initrd.img.old

and /boot has the following:
root@mw-monitor:/usr/src# ls -la /boot
total 225820
drwxr-xr-x  3 root root  4096 Dec  2 09:00 .
drwxr-xr-x 23 root root  4096 Nov 29 13:08 ..
lrwxrwxrwx  1 root root 1 Nov 29 09:50 boot -> .
-rw-r--r--  1 root root127403 Apr 30  2016 config-4.5.0-2-sparc64-smp
-rw-r--r--  1 root root131092 Nov 12 22:38 config-4.8.0-1-sparc64-smp
lrwxrwxrwx  1 root root 1 Nov 29 09:50 etc -> .
-rw-r--r--  1 root root  1024 Jan 22  2016 fd.b
-rw-r--r--  1 root root   512 Jan 22  2016 first.b
-rw-r--r--  1 root root  1024 Jan 22  2016 generic.b
-rw-r--r--  1 root root   800 Jan 22  2016 ieee32.b
lrwxrwxrwx  1 root root30 Nov 29 11:28 initrd.img ->
initrd.img-4.8.0-1-sparc64-smp
-rw-r--r--  1 root root  17087722 Nov 29 11:07
initrd.img-4.5.0-2-sparc64-smp
-rw-r--r--  1 root root  17459632 Nov 29 13:10
initrd.img-4.8.0-1-sparc64-smp
-rw-r--r--  1 root root 183723635 Dec  2 09:00 initrd.img-4.8.11
lrwxrwxrwx  1 root root30 Nov 29 11:28 initrd.img.old ->
initrd.img-4.5.0-2-sparc64-smp
-rw-r--r--  1 root root  6752 Jan 22  2016 isofs.b
drwx--  2 root root 16384 Nov 29 09:13 lost+found
-rw-r--r--  1 root root  7680 Nov 29 09:50 old.b
-rw-r--r--  1 root root 53760 Nov 29 09:50 second.b
-rw-r--r--  1 root root   235 Dec  2 09:02 silo.conf
-rw-r--r--  1 root root 51437 Jan 22  2016 silotftp.b
-rw-r--r--  1 root root   2314500 Apr 30  2016
System.map-4.5.0-2-sparc64-smp
-rw-r--r--  1 root root   2388680 Nov 12 22:38
System.map-4.8.0-1-sparc64-smp
-rw-r--r--  1 root root   512 Jan 22  2016 ultra.b
lrwxrwxrwx  1 root root27 Nov 29 11:28 vmlinuz ->
vmlinuz-4.8.0-1-sparc64-smp
-rw-r--r--  1 root root   3715429 Apr 30  2016 vmlinuz-4.5.0-2-sparc64-smp
-rw-r--r--  1 root root   3824109 Nov 12 22:38 vmlinuz-4.8.0-1-sparc64-smp
lrwxrwxrwx  1 root root27 Nov 29 11:28 vmlinuz.old ->
vmlinuz-4.5.0-2-sparc64-smp

looking at the directory I'm wondering;
1) do I need to change the