Hi Geert,
after some updates this bug did not appear on my 64-bit notebook again, but it
still appears on my EEEPC, which has the same package versions as my 64-bit
notebook, except that all packages are 32-bit.
I added a new file of dmesg output fropm my EEEPC. I hope it helps.
Please feel fr
Hi Geert,
after some updates this bug did not appear on my 64-bit notebook again, but it
still appears on my EEEPC, which has the same package versions as my 64-bit
notebook, except that all packages are 32-bit.
I added a new file of dmesg output fropm my EEEPC. I hope it helps.
Please feel fr
Hi Geert,
maybe you should also know, that I am NOT using network manager.
Additionally I am using fixed ip-addresses, so that I am online without the
need of wicd or network-manager.
Although I have configured eth0, it is not connected to the cable, as I am
using wireless connection.
I send y
Control: tag -1 -moreinfo
On Thu, Oct 08, 2015 at 07:37:55PM +0200, Hans wrote:
> >cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 root=UUID=changed_by_me_to_be_secret ro
> quiet
> I also attached the output of dmesg in the file kernelringbuffer.txt
Thanks
Hi Geert,
thank you for your patience. Sorry, i had to fix some other unrelated things.
> sent the output of
>
>cat /proc/cmdline
>
Here it is:
snip --
BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 root=UUID=changed_by_me_to_be_secret ro
quiet
snap ---
> to t
On Sat, Oct 03, 2015 at 07:44:22PM +0200, Hans wrote:
> Am Samstag, 3. Oktober 2015, 19:02:53 schrieb Geert Stappers:
> > Please provide more information, example given:
> > * Log messages
> Sorry, I believe,
> there are no usable logfiles available as it happens at boot.
There is `dmesg`, do
Am Samstag, 3. Oktober 2015, 19:02:53 schrieb Geert Stappers:
Hi Geert,
I will see, if I can help.
>
> Please provide more information, example given:
>
> * Log messages
Sorry, I believe, there are no usable logfiles available as it happens at
boot.
> * Hardware being used
The problem appe
Control: tag -1 moreinfo
On Sat, Oct 03, 2015 at 06:42:49PM +0200, Hans wrote:
>
> When the system boots up and the network shall be activated, the system
> hangs for a long time (about 2 minutes). Then the systemd-counter
> shows up and after the waiting time (about the mentioned 2 minutes),
> th
Package: linux-image-4.2.0-1-amd64
Version: 4.2.1-2
Severity: important
Dear maintainer-team,
there is a very annoying problem, I discovered with all kernels since version
4.X.
When the system boots up and the network shall be activated, the system hangs
for
a long time (about 2 minutes). Then
9 matches
Mail list logo