Sorry to bring this up.
I just wanted to say that, after a dist-upgrade, the latest Linux kernel
from Jessie backports (4.9.0) boots just fine.
I could never known what was wrong with Linux 4.7.
Thanks for your support,
Emiliano.
On Mon, Dec 19, 2016 at 10:09 PM, Brad Campbell
wrote:
> On 20
On 12/19/2016 10:08 PM, marc wrote:
> And completely unrelated: The devuan I have doesn't mount the
> cgroup fs (debian seems to rely on systemd to that), so if you want
> to use lxc, you might want to add
>
> mount -t cgroup cgroup /sys/fs/cgroup
>
> to your startup scripts.
I'm using the cgroup
On 20/12/16 06:08, marc wrote:
Hi devuanfanboy,
Thanks but no, that dind't work.
I have also had an interesting time getting the devuan beta to
run with a newer kernel.
In my case I have forgone the entire initrd, and built the newest
stable kernel from kernel.org with the necessary drivers b
> Hi devuanfanboy,
>
> Thanks but no, that dind't work.
I have also had an interesting time getting the devuan beta to
run with a newer kernel.
In my case I have forgone the entire initrd, and built the newest
stable kernel from kernel.org with the necessary drivers built in.
In some kernel c
Hi devuanfanboy,
Thanks but no, that dind't work.
On Sat, Dec 17, 2016 at 1:11 PM, wrote:
> I have one suggestion for how to fix the problem.
>
> Try using a traditional device node, instead of booting with the root
> partition set as a UUID. The UUID may have changed over kernel upgrade.
>
> H
Hi again, Emiliano
On 12/16/2016 05:03 PM, Emiliano Marini wrote:
I did purge and install the 4.7 kernel.
I have recreated the initrd using dpkg-reconfigure linux-image...
previously.
Now I tried mkinitramfs as you suggested:
root@devuan:/home/emi# mkinitramfs -o /boot/initrd.img-4.7.0-0.bpo
I have one suggestion for how to fix the problem.
Try using a traditional device node, instead of booting with the root
partition set as a UUID. The UUID may have changed over kernel upgrade.
Have a look in /etc/fstab to find the right device node for "/"
And edit your grub configuration line
Hi Emiliano,
On 12/16/2016 05:03 PM, Emiliano Marini wrote:
I did purge and install the 4.7 kernel.
I have recreated the initrd using dpkg-reconfigure linux-image...
previously.
Now I tried mkinitramfs as you suggested:
root@devuan:/home/emi# mkinitramfs -o /boot/initrd.img-4.7.0-0.bpo.1-686.
On Fri, Dec 16, 2016 at 07:32:44PM +0100, Adam Borowski wrote:
> On Fri, Dec 16, 2016 at 05:34:41PM +, KatolaZ wrote:
> > What I am trying to say is that you can donwload a vanilla kernel from
> > www.kernel.org, e.g. one that does not have that bug (which seems to
> > have been introduced by o
On Fri, Dec 16, 2016 at 05:34:41PM +, KatolaZ wrote:
> What I am trying to say is that you can donwload a vanilla kernel from
> www.kernel.org, e.g. one that does not have that bug (which seems to
> have been introduced by one of the Debian patches) and produce a deb
> package for it using kern
On Fri, Dec 16, 2016 at 02:10:45PM -0300, Emiliano Marini wrote:
> Thanks KatolaZ,
>
> I was trying that, but once I saw "4.7.8-1" I stopped immediately because
> of that bug reported on the Debian bug track.
>
> It was nice learning some things though.
>
What I am trying to say is that you can
Thanks KatolaZ,
I was trying that, but once I saw "4.7.8-1" I stopped immediately because
of that bug reported on the Debian bug track.
It was nice learning some things though.
On Fri, Dec 16, 2016 at 2:02 PM, KatolaZ wrote:
> On Fri, Dec 16, 2016 at 01:40:49PM -0300, Emiliano Marini wrote:
>
On Fri, Dec 16, 2016 at 01:40:49PM -0300, Emiliano Marini wrote:
> Update:
>
> I just downloaded the source code for this kernel through apt-get source
> linux and got this:
>
> root@devuan:/usr/local/src# ll
> total 92204
> drwxr-xr-x 26 root root 4096 dic 16 13:39 linux-4.7.8
> -rw-r--r--
Ups!
Reattempted running:
mkinitramfs -o /boot/initrd.img-4.7.0-0.bpo.1-686.emi 4.7.0-0.bpo.1-686
Anyway, same result. The kernel won't even try to decompress the initrd.
On Fri, Dec 16, 2016 at 1:47 PM, Alessandro Selli wrote:
> Il giorno Fri, 16 Dec 2016 11:22:58 -0300
> Emiliano Marini h
Update:
I just downloaded the source code for this kernel through apt-get source
linux and got this:
root@devuan:/usr/local/src# ll
total 92204
drwxr-xr-x 26 root root 4096 dic 16 13:39 linux-4.7.8
-rw-r--r-- 1 root staff 2666180 oct 19 22:02
linux_4.7.8-1~bpo8+1.debian.tar.xz
-rw-r--r--
Il giorno Fri, 16 Dec 2016 11:22:58 -0300
Emiliano Marini ha scritto:
> I did purge and install the 4.7 kernel.
>
> I have recreated the initrd using dpkg-reconfigure linux-image...
> previously.
>
> Now I tried mkinitramfs as you suggested:
>
> root@devuan:/home/emi# mkinitramfs -o /boot/init
Indeed:
root@devuan:/boot# grep _RD_ config-4.7.0-0.bpo.1-686
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
On Fri, Dec 16, 2016 at 11:58 AM, KatolaZ wrote:
> On Fri, Dec 16, 2016 at 11:22:58AM -0300, Emiliano Marini wrote:
> > I did purge a
On Fri, Dec 16, 2016 at 11:22:58AM -0300, Emiliano Marini wrote:
> I did purge and install the 4.7 kernel.
>
> I have recreated the initrd using dpkg-reconfigure linux-image...
> previously.
>
> Now I tried mkinitramfs as you suggested:
>
> root@devuan:/home/emi# mkinitramfs -o /boot/initrd.img-
I did purge and install the 4.7 kernel.
I have recreated the initrd using dpkg-reconfigure linux-image...
previously.
Now I tried mkinitramfs as you suggested:
root@devuan:/home/emi# mkinitramfs -o /boot/initrd.img-4.7.0-0.bpo.1-686.emi
Booted using this new initrd, same results :( I'm getting
On Fri, Dec 16, 2016 at 11:08:10AM -0300, Emiliano Marini wrote:
> The 4.6 kernel could extract my .xz initrd though.
>
Have you tried recreating the initrd with initramfs-tools? (or just by
purging and reinstalling the 4.7 kernel package?)
HND
KatolaZ
--
[ ~.,_ Enzo Nicosia aka KatolaZ - GL
The 4.6 kernel could extract my .xz initrd though.
On Fri, Dec 16, 2016 at 11:06 AM, Emiliano Marini <
emilianomarin...@gmail.com> wrote:
> Alright,
>
> I did this:
>
> root@devuan:~# mkdir -p /tmp/initrd
> root@devuan:~# cd /tmp/initrd
> root@devuan:/tmp/initrd# zcat /boot/initrd.img-4.7.0-0.bpo
Alright,
I did this:
root@devuan:~# mkdir -p /tmp/initrd
root@devuan:~# cd /tmp/initrd
root@devuan:/tmp/initrd# zcat /boot/initrd.img-4.7.0-0.bpo.1-686 | cpio
-idmv 2>/dev/null
root@devuan:/tmp/initrd# ls
bin conf etc init lib run sbin scripts
root@devuan:/tmp/initrd# find . | cpio -o -c |
On Fri, Dec 16, 2016 at 01:56:19PM +, KatolaZ wrote:
[cut]
>
> apt-get install xz-utils
>
> and then recreate the initramfs again. If xz is available, initramfs
^^
Sorry, I meant "initramfs-tools" there, and not "initram
On Fri, Dec 16, 2016 at 10:13:05AM -0300, Emiliano Marini wrote:
>
> I tried the 4.6 kernel with the 4.7 initrd and it almost boot (at the end
> init cannot access the root fs device). But the 4.6 kernel extracts the 4.7
> initrd and loads de init process. This leads me to think it's a kernel
> i
Hi KatolaZ,
It's gzip compressed:
emi@devuan:~$ file /boot/initrd.img-4.7.0-0.bpo.1-686
/boot/initrd.img-4.7.0-0.bpo.1-686: gzip compressed data, last modified:
Fri Dec 16 09:32:51 2016, from Unix
It unpacks ok:
emi@devuan:~$ mkdir -p /tmp/initrd
emi@devuan:~$ cd /tmp/initrd
emi@devuan:/tmp/ini
On Fri, Dec 16, 2016 at 08:21:11AM -0300, Emiliano Marini wrote:
> I've got rid of that error installing the kernel headers. But nothing has
> changed.
>
> apt-get install linux-headers-4.7.0-0.bpo.1-all
> apt-get install --reinstall linux-image-4.7.0-0.bpo.1-686
>
This definitely looks to me as
I've got rid of that error installing the kernel headers. But nothing has
changed.
apt-get install linux-headers-4.7.0-0.bpo.1-all
apt-get install --reinstall linux-image-4.7.0-0.bpo.1-686
On Fri, Dec 16, 2016 at 8:07 AM, Emiliano Marini wrote:
> This kernel comes from Jessie backports:
>
> roo
This kernel comes from Jessie backports:
root@devuan:/home/emi# apt-cache showpkg linux-image-4.7.0-0.bpo.1-686
Package: linux-image-4.7.0-0.bpo.1-686
Versions:
4.7.8-1~bpo8+1
(/var/lib/apt/lists/ar.mirror.devuan.org_merged_dists_jessie-backports_main_binary-i386_Packages)
(/var/lib/dpkg/status)
Yes, make it the default using dpkg-reconfigure grub-pc (remove the
'quiet' line altogether). You might need to change debconf priority to
low see that prompt though, e.g dpkg-reconfigure debconf first.
Do the keyboard LED's flash when you try to boot? If so the kernel is
loading but panicking
I would check that tomorrow because right now I have no access to my VM.
On Thu, Dec 15, 2016 at 3:21 PM, Florian Zieboll wrote:
> On Thu, 15 Dec 2016 08:45:39 -0300
> Emiliano Marini wrote:
>
> > I have updated my Devuan VM:
> >
> > apt-get update && apt-get upgrade && apt-get dist-upgrade
> >
I have recreated the initrd using:
dpkg-reconfigure linux-image-4.7.0-0.bpo.1-686
Same results. Not blinking cursor after trying to load de initramfs.
On Thu, Dec 15, 2016 at 12:19 PM, KatolaZ wrote:
> On Thu, Dec 15, 2016 at 12:11:46PM -0300, Emiliano Marini wrote:
> > Nothing,
> >
> > I've
On Thu, Dec 15, 2016 at 08:50:40PM +0100, Miroslav Rovis wrote:
[cut]
>
> May perfectly be as you write, kind veteran Unix Admin.
>
> However, I now remember I did have (well, on Gentoo, but it's the Unix
> version of Gentoo, not the systemd version, and I remember often issues were
> similar
On Thu, Dec 15, 2016 at 05:44:49PM -0300, Emiliano Marini wrote:
> Yes, I've got the same blank screen, with the not-blinking cursor on the
> top left corner, after the "loading the initrd" message.
>
So, technically, you don't have a blank screen, since you see at least
the non-blknking cursor :
Yes, I've got the same blank screen, with the not-blinking cursor on the
top left corner, after the "loading the initrd" message.
On Thu, Dec 15, 2016 at 12:44 PM, Alessandro Selli <
alessandrose...@linux.com> wrote:
> Il giorno Thu, 15 Dec 2016 12:14:06 -0300
> Emiliano Marini ha scritto:
>
> >
On 161215-20:50+0100, Miroslav Rovis wrote:
> Just worth trying, maybe... Some issues with memory and swap could be
> overcome that way.
Oh, no, not sway of course, but the RAM issues. Let it all purge out
from RAM, just in case.
--
Miroslav Rovis
Zagreb, Croatia
http://www.CroatiaFidelis.hr
s
On 161215-19:31+, KatolaZ wrote:
> On Thu, Dec 15, 2016 at 08:14:25PM +0100, Miroslav Rovis wrote:
>
> [cut]
>
> >
> > It's related with ATI cards, but with the newer kernel than yours, so...
> >
> > (And there are some issues with some Nvidia cards on Gentoo users ML too.)
> >
> > Certain
On Thu, Dec 15, 2016 at 08:14:25PM +0100, Miroslav Rovis wrote:
[cut]
>
> It's related with ATI cards, but with the newer kernel than yours, so...
>
> (And there are some issues with some Nvidia cards on Gentoo users ML too.)
>
> Certainly, blank screen can indicate problems with graphics card
On 161215-08:45-0300, Emiliano Marini wrote:
> I have updated my Devuan VM:
>
> apt-get update && apt-get upgrade && apt-get dist-upgrade
>
> But it won't boot with Linux 4.7, I just get a blank screen right after the
> GRUB menu:
Just maybe related, in Gentoo-users there is an issue involving b
On Thu, 15 Dec 2016 08:45:39 -0300
Emiliano Marini wrote:
> I have updated my Devuan VM:
>
> apt-get update && apt-get upgrade && apt-get dist-upgrade
>
> But it won't boot with Linux 4.7, I just get a blank screen right
> after the GRUB menu:
Hallo Emiliano,
did you look into the upgrade-log
On Thu, 15 Dec 2016 15:26:22 +0100
Alessandro Selli wrote:
> Il giorno Thu, 15 Dec 2016 13:34:25 -
> devuanfan...@use.startmail.com ha scritto:
> > Try removing the 'quiet' line, this should give you some output
> > when booting.
>
> Speaking about which, I'd set this as a default GRUB
Il giorno Thu, 15 Dec 2016 12:14:06 -0300
Emiliano Marini ha scritto:
> Tried the 4.7.0-0.bpo.1-686-pae kernel (enabling PAE/NX in VirtualBox
> config) with same results.
Did you try the debug option?
> On Thu, Dec 15, 2016 at 12:12 PM, Alessandro Selli <
> alessandrose...@linux.com> wrote:
On Thu, Dec 15, 2016 at 12:11:46PM -0300, Emiliano Marini wrote:
> Nothing,
>
> I've got the same blank screen, with the not-blinking cursor on the top
> left corner, after the "loading the initrd" message.
>
Could it be the case that the initrd is corrupted/misses something?
Have you tried to r
Tried the 4.7.0-0.bpo.1-686-pae kernel (enabling PAE/NX in VirtualBox
config) with same results.
On Thu, Dec 15, 2016 at 12:12 PM, Alessandro Selli <
alessandrose...@linux.com> wrote:
> Il giorno Thu, 15 Dec 2016 11:51:05 -0300
> Emiliano Marini ha scritto:
>
> > How could I check the logs if th
Nothing,
I've got the same blank screen, with the not-blinking cursor on the top
left corner, after the "loading the initrd" message.
On Thu, Dec 15, 2016 at 12:02 PM, Alessandro Selli <
alessandrose...@linux.com> wrote:
> Il giorno Thu, 15 Dec 2016 11:51:05 -0300
> Emiliano Marini ha scritto:
Il giorno Thu, 15 Dec 2016 11:51:05 -0300
Emiliano Marini ha scritto:
> How could I check the logs if the kernel isn't loading? There is any way to
> see GRUB logs besides removing the "quiet" option?
Try adding the debug option.
--
Alessandro Selli http://alessandro.route-add.net
VOIP SIP:
How could I check the logs if the kernel isn't loading? There is any way to
see GRUB logs besides removing the "quiet" option?
Tried to reinstall that kernel image:
apt-get purgue linux-image-4.7.0
apt-get upgrade linux-image-686
Same kernel 4.7, nothing changed.
Thanks,
Emiliano.
On Thu, De
Nothing,
Blank screen after the last grub's echo.
:(
On Thu, Dec 15, 2016 at 10:34 AM, wrote:
> From your screenshot edit of the grub command line:
> https://imgur.com/aSVp1UG
>
> Try removing the 'quiet' line, this should give you some output when
> booting.
>
> On Thursday, December 15, 2016
Il giorno Thu, 15 Dec 2016 13:34:25 -
devuanfan...@use.startmail.com ha scritto:
> From your screenshot edit of the grub command line:
> https://imgur.com/aSVp1UG
>
> Try removing the 'quiet' line, this should give you some output when
> booting.
Speaking about which, I'd set this as a d
Thank you, I'll try this and see what happens.
On Thu, Dec 15, 2016 at 10:34 AM, wrote:
> From your screenshot edit of the grub command line:
> https://imgur.com/aSVp1UG
>
> Try removing the 'quiet' line, this should give you some output when
> booting.
>
> On Thursday, December 15, 2016 12:58 P
From your screenshot edit of the grub command line:
https://imgur.com/aSVp1UG
Try removing the 'quiet' line, this should give you some output when
booting.
On Thursday, December 15, 2016 12:58 PM, Alessandro Selli
wrote:
Il giorno Thu, 15 Dec 2016 08:45:39 -0300
Emiliano Marini ha scr
Il giorno Thu, 15 Dec 2016 08:45:39 -0300
Emiliano Marini ha scritto:
> What could possibly be wrong with the new kernel?
Please, check the logs of the failed boot.
--
Alessandro Selli http://alessandro.route-add.net
VOIP SIP: dhatarat...@ekiga.net
Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9
_
I have updated my Devuan VM:
apt-get update && apt-get upgrade && apt-get dist-upgrade
But it won't boot with Linux 4.7, I just get a blank screen right after the
GRUB menu:
http://imgur.com/7NCZitR
If I edit the GRUB line, it boots ok with Linux 4.6:
http://imgur.com/aSVp1UG
My /boot directo
52 matches
Mail list logo
