Selective connection problem

[kyodev]

1) The rest of the system will be OK if I downgrade, right? It would be just the kernel.
3) How can I modify grub 2 configuration? Because I can just make 3.2.0-4 my default

yes, if you downgrade, you will have another choice with kernel 3.2, for test it.
first, preserve this two choices, test 3.2.
later, you will delete or hide the kernel you want
downgrade:

Code: Select all

su

# add wheezy repository
echo 'deb http://http.debian.net/debian wheezy main' > /etc/apt/sources.list.d/99-wheezy.list
apt-get update

#search kernel
apt search linux-image-3.2

#for 64bits:
apt-get install linux-image-3.2.0-4-amd64 linux-headers-3.2.0-4-amd64
#for 32bits	PAE
apt-get install linux-image-3.2.0-4-686-pae linux-headers-3.2.0-4-686-pae
#for 32bits
apt-get install linux-image-3.2.0-4-486 linux-headers-3.2.0-4-486

#if you have a nvidia graphic card:
sudo apt-get install --reinstall nvidia-kernel-dkms

#remove wheezy repository
rm /etc/apt/sources.list.d/99-wheezy.list
apt-get update ; apt-get autoclean


#update gru
update-grub
	
reboot

[Gonzalo_VC]

But I already have it: Linux gonzalo-home 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux

[timber]

PS: I already asked for a script to remove older kernels easy. Otherwise, being a semi-rolling release distribution, we'll end up with 2 pages of booting menu in sometime

Hi Gonzalo_VC,

I've learned from past experience that it's always a good idea to keep the last kernel to fall back on if needed.
Doing so has saved me more than once.

A good backup may also be helpful, but restoring a backup takes much longer than just selecting the earlier kernel in grub to get back on track. You script could probably be edited to save current and most recent past kernel.

[kyodev]

ok, so why not downgrade the kernel to 3.2 with wheezy repo?

2) How do I do that?
But I already have it: Linux gonzalo-home 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux

hi,
I don't understand, you have posted a inxi report with 3.9 kernel.
if you have 3.2 kernel, you can see if connection problem is solved.
It's better with it?
if no, you must forget the kernel version et look carefully the network configuration.

[Gonzalo_VC]

ok, so why not downgrade the kernel to 3.2 with wheezy repo?

2) How do I do that?
But I already have it: Linux gonzalo-home 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux

hi,
I don't understand, you have posted a inxi report with 3.9 kernel.

That's because it reports what you have in the session you're running. But in the machine I already have 3 kernels since the fresh install to the last (2nd) major update the distro undergo.
I have explained that in my first big post, I hope.

if you have 3.2 kernel, you can see if connection problem is solved.
It's better with it?
if no, you must forget the kernel version et look carefully the network configuration.

The problem is that I figured out that the newer kernels had something to do after many "experiments".
Yes, I can boot with 3.2 and use it. But that is not the long term solution, since I would have to upgrade the kernel, eventually; cannot go forever with 3.2.
I am downloading the latest ISO and will install it formating the "/" partition. I think it has the 3.9 kernel, but I'll test it in a live session, before, to see if I can connect.
This will be my last attempt before changing the distro in that machine.

[kyodev]

since I would have to upgrade the kernel, eventually; cannot go forever with 3.2....
I am downloading the latest ISO and will install it formating the "/" partition. I think it has the 3.9 kernel

the kernel 3.2 is the debian stable kernel, it is not outdated.

with kernel 3.2, connection is good ?

the last iso is with kernel 3.9. after you have to september update with kernel 3.10.

unfortunately, you can't compare a live session (without configuration) with an operating system, I think.
if you switch to another distro, you will also have recent kernels... and a clean install.
for example, as you say, a live SolydK64 works, no?

.

[Gonzalo_VC]

the kernel 3.2 is the debian stable kernel, it is not outdated.
with kernel 3.2, connection is good ?

YES. I have said so.

the last iso is with kernel 3.9. after you have to september update with kernel 3.10.

I know. I'm in a live session now: Linux solydxk 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 GNU/Linux

unfortunately, you can't compare a live session (without configuration) with an operating system, I think.
if you switch to another distro, you will also have recent kernels... and a clean install.
for example, as you say, a live SolydK64 works, no?

I can connect with other distros, persistent or live-sessions. It's true they have older (stable) kernels

Nevertheless. I'll format and reinstall SolydK64 here. Wish me luck.

Mmmm I can see you-tube videos, login yahoo mail, but posting here is no good, yet!!??
I guess is better to boot with kenel 3.2, remove the others with synaptic, update grub, and wait to see what future is bringing.
An important detail is to reinstall VirtualBox and some other things that are modified according to the kernel we are running.

[Gonzalo_VC]

At work, I'm updating my other 8 machines. So far so good. This crazy %$# @$#@ issue is only at home.

One detail that appears and I guess you have notices it: this message
"/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated

Cheers!

[Gonzalo_VC]

OK, OK, OK! Stop the presses!
A friend pointed me to some log files in var/log/messages. I tried to acess the sites I can't, just to see the log of it, and I got this weird sentence many times (the first one, copied just twice here) and the the other mentioning kernel:

Sep 16 20:37:59 gonzalo-home org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Sep 16 22:07:06 gonzalo-home org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Sep 16 22:14:54 gonzalo-home kernel: [38599.895566] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state

Any clues!? The folder /sys/kernel/debug/ is empty!

[kyodev]

"/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated

hello
it's just a warning, you can see that:
http://forums.solydxk.nl/viewtopic.php?f=13&t=1424

[kyodev]

Sep 16 22:07:06 gonzalo-home org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.

for me, when I unplug my netbook and when battery work:
Sep 17 14:57:02 1201nl org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
but everything is ok.

for the kernel message I don't know, but perhaps ypu can list pour all <arnings:
cat /var/log/kern.log

on google, it seems only match the graphic card:
https://www.google.com/webhp?q=[drm]+ca ... rror+event

[Gonzalo_VC]

Is it safe to remove all this?? (and stay with kernel 3.2.4, only?)

[kyodev]

yes, it'safe BUT /!\ warning /!\:
you must conserve linux-(image|headers)-amd64 for the next update, if you want have the future kernel for testing.
finally, if I inderstand all, with just change 3.2 kernel, your connection is good? (I would not have thought)

[Gonzalo_VC]

yes, it'safe BUT /!\ warning /!\:
you must conserve linux-(image|headers)-amd64 for the next update, if you want have the future kernel for testing.
finally, if I inderstand all, with just change 3.2 kernel, your connection is good? (I would not have thought)

I'll try to keep that one... if Synaptic does not remove it automatically (dependence process), or re-install it, in that case.
Yes, with 3.2 I can do the things the newer kernels prevent me to do, including posting here, seeing youtube videos, working with some web-mail...
Weird, eh!?

[kyodev]

strange yes, glad for you it you can now post here without worry

[Gonzalo_VC]

Well, well. I remove those, and tried to reinstall the heathers and image for future kernel upgrades and all, as suggested by kyodev.
But first I got "broken packages" messages. I cleaned apt-get in the terminal, made other "mambo-jambo geek moves" and marked those for install. So, the system dis what? Installed the last one (3.10). It was that or nothing.

In summary: I got rid of 3.09 ... and have to select 3.2 in the grub menu at boot, so I can post here. Nevermind,
I'll find out, during the weekend, how to edit cryptic grub 2. I did it once, but can't remember now. It's not so easy as in 1.x version.
Cheers.

add.png (36.78 KiB) Viewed 3693 times

[kyodev]

tried to reinstall the heathers and image for future kernel upgrades and all, as suggested by kyodev

sorry, I was not clear. I just wanted to suggest to preserve, if you want a future dist-upgrade of kernel:
linux-image-amd64
or for other:
linux-image-686-pae
inux-image-486

then you can

Code: Select all

su
apt-get purge linux-.*-3.10-2-amd64
# you can verify that you have linux-image-amd64 always installed:
dpkg -l linux-image-amd64

comment: if you remove inux-image-architecture, it will be safe, but you must manually update a future kernel.

how to edit cryptic grub 2. I did it once, but can't remember now.

yes it's not easy, you can wait, soon there will be grub-customizer in repo.

[kyodev]

you can now test this package of grub-customizer:
http://forums.solydxk.nl/viewtopic.php?f=58&t=1505

[Gonzalo_VC]

you can now test this package of grub-customizer:
http://forums.solydxk.nl/viewtopic.php?f=58&t=1505

I'll try. Thank you.

[Gonzalo_VC]

PS: just to keep you updated, I gave up on that machine.