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 somethi
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:
>>
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:
>>
>
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
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 configu
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
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.debia
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 SM
On 11/30/2016 2:43 AM, Anatoly Pugachev wrote:
>> $ 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 (Jus
> $ 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)
or instead of "
On 11/29/2016 11:43 PM, John Paul Adrian Glaubitz wrote:
> Try:
>
> $ 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)
Oops, tha
On 11/29/2016 11:33 PM, rod wrote:
> 1) I have noodled around with this all day (slow day here) and I'm not
> any closer to understanding the process to compile the 4.8.11 kernel. If
> you could point me to a HOWTO or other documentation by which I can
> further my knowledge and understanding of th
>> That's a bug I fixed, but it didn’t make it into the 4.8 branch until
>> 4.8.10[1]. Unfortunately that’s not yet been packaged for Debian. There
>> is 4.9~rc5-1~exp1 in experimental, but I haven’t tried that build, and I
>> don’t know if the serious regression of not being able to load kernel
>
...
>> Using the above thread and after installing several packages (apache2,
>> mariadb, phpmyadmin, webmin, & shellinabox and their associated
>> requirement packages); I got the following crash and had to reboot.
...
>> [ 3061.611384] \|/ \|/
>> [ 3061.611384] "
> On 28 Nov 2016, at 22:07, rod wrote:
>> On 11/18/2016 4:32 PM, John Paul Adrian Glaubitz wrote:
>>> On 11/16/2016 06:13 PM, rod wrote:
>>> The current problem I'm having is this:
>>>
>>> root@mw-monitor:/home/rod# aptitude
>>> Ouch! Got SIGSEGV, dying..
>>> Segmentation fault
>>
>> This has t
On 11/28/2016 4:07 PM, rod wrote:
>
>
> On 11/18/2016 4:32 PM, John Paul Adrian Glaubitz wrote:
>> On 11/16/2016 06:13 PM, rod wrote:
>>> The current problem I'm having is this:
>>>
>>> root@mw-monitor:/home/rod# aptitude
>>> Ouch! Got SIGSEGV, dying..
>>> Segmentation fault
>>
>> This has tur
On 11/18/2016 4:32 PM, John Paul Adrian Glaubitz wrote:
> On 11/16/2016 06:13 PM, rod wrote:
>> The current problem I'm having is this:
>>
>> root@mw-monitor:/home/rod# aptitude
>> Ouch! Got SIGSEGV, dying..
>> Segmentation fault
>
> This has turned out to be an issue with libstdc++6 which come
On 11/19/2016 01:13 PM, John Paul Adrian Glaubitz wrote:
> Ok, the last fix for binutils was yet not enough. The problem was supposedly
> introduced by this change in binutils [1]. We have reverted this change now
> completely and are rebuilding gcc-6 again.
This works now. Just make sure to insta
On 11/18/2016 11:32 PM, John Paul Adrian Glaubitz wrote:
> This has turned out to be an issue with libstdc++6 which comes from the gcc-6
> package which was built with a broken version of binutils. The buildds are
> currently building a fresh gcc-6 package which is being built with a fixed
> versio
On 11/16/2016 06:13 PM, rod wrote:
> The current problem I'm having is this:
>
> root@mw-monitor:/home/rod# aptitude
> Ouch! Got SIGSEGV, dying..
> Segmentation fault
This has turned out to be an issue with libstdc++6 which comes from the gcc-6
package which was built with a broken version of bi
On 11/16/2016 4:30 PM, James Clarke wrote:
>> On 16 Nov 2016, at 22:26, rod wrote:
>>> On 11/16/2016 2:12 PM, rod wrote:
On 11/16/2016 1:32 PM, James Clarke wrote:
Hi Rod,
> On 16 Nov 2016, at 17:13, rod wrote:
>
> I followed the guide you wrote (after dumping debian for s
> On 16 Nov 2016, at 22:26, rod wrote:
>> On 11/16/2016 2:12 PM, rod wrote:
>>> On 11/16/2016 1:32 PM, James Clarke wrote:
>>> Hi Rod,
On 16 Nov 2016, at 17:13, rod wrote:
I followed the guide you wrote (after dumping debian for solaris to
reset the sc> password). It works we
OK so new question...
Once I've done the reinstall from the archive should I do apt-get update
&& apt-get upgrade followed by apt-get dist-upgrade? Will it grab from
the newly built packages? Will it bork the newly installed system?
Rod
On 11/16/2016 2:12 PM, rod wrote:
> Thanks James. I did lo
Thanks James. I did look at the buildd page and saw large number
working on being rebuilt and thought it might be something like this.
I will change the mirror and reload simple for quickness.
I figured it was better to mention it...
Rod
On 11/16/2016 1:32 PM, James Clarke wrote:
> Hi Rod,
>>
Thanks James. I did look at the buildd page and saw large number
working on being rebuilt and thought it might be something like this.
I will change the mirror and reload simple for quickness.
I figured it was better to mention it...
Rod
On 11/16/2016 1:32 PM, James Clarke wrote:
> Hi Rod,
>>
Hi Rod,
> On 16 Nov 2016, at 17:13, rod wrote:
>
> I followed the guide you wrote (after dumping debian for solaris to
> reset the sc> password). It works well as written, covering all the
> issues that came up.
>
> The current problem I'm having is this:
>
> root@mw-monitor:/home/rod# aptitude
Adrian,
I followed the guide you wrote (after dumping debian for solaris to
reset the sc> password). It works well as written, covering all the
issues that came up.
The current problem I'm having is this:
root@mw-monitor:/home/rod# aptitude
Ouch! Got SIGSEGV, dying..
Segmentation fault
or
roo
27 matches
Mail list logo
