LMDE BREAKAGES - tracking TESTING

[viking777]

So again, are you still using smxi-sgfxi,

Well remembered Chris! I did use sgfxi for quite a while, but I switched back to dkms a couple of days before this problem occurred - ironically to prevent me having to run sgfxi every time I got an xorg, nvidia or kernel update

[Chris M]

OK, viking. That was my first kernel update since using sgfxi, and now I remember you indicating that you had to run sgfxi every time a new kernel came through, and that it would dump you into a command/login prompt. Thanks.

[kruijf]

Today i had a system logout whit chrome and FireFox by opening a link on the site www.flabber.nl
The link about the turnster, its a video. But i realy dont know yet what the solution is.
What is bether to use aptitude or the updatemanager?

[kruijf]

I think i found it, it seems to be its a flash problem.
I found this site http://richardjaustin.co.uk/gnome-3-fla ... -to-logout
And he is speaking about untick “Enable hardware acceleration” this is what i done.
So far so good.

[zerozero]

kruijf, glad you got it sorted

[kruijf]

kruijf, glad you got it sorted

For a short while yes, the problem is back again.
I realy dont know what it is any more.
It looks like Empathy give's the same problem, but that i think its weird.

[kruijf]

Today again 3 time's that gnome 3 logs me out, i must log in again.
Today it was again whit visiting a site ( www.flabber.nl )
I dont know any more where to look, some one else have any idea's???

[nimbvs]

debtags stopped working today. See Debian bug #660222.
I had to uninstall debtags.

[kruijf]

debtags stopped working today. See Debian bug #660222.
I had to uninstall debtags.

Can you tell us for who this is?

[nimbvs]

It isn't for anybody. It's just a warning, in case anybody else has issues with this package.

[thioz]

Hi guys,

I experienced the breakage of the broadcom-sta drivers in 3.2.0.1-686 kernel.

Switching to the b43-fwcutter did bring my wireless back up and it's working pretty well.

hope it helps someone

Cheers

[kruijf]

It isn't for anybody. It's just a warning, in case anybody else has issues with this package.

Alright thanks, i whas confused becaus i didnt saw a question about it.

[Chris M]

This question is in regards to kruijf's "flash issue", which may be about new kernel installation.

The new 3.2 kernel came through. No problems for me, but on my Intel everything laptop when the 3.1 kernel came out, I had to manually install it through synaptic, which I thought was weird at the time.

On my system, for this new 3.2 kernel (and I'm on my desktop right now with an Intel chipset and nvidia card), it's a given that you need:

linux-image-3.2.0-1-686-pae
linux-headers-3.2.0-1-686-pae
linux-headers-3.2.0-1-common (I think this one is needed)

But besides the numbered linux-image and linux-headers files, there are also generic (unnumbered) meta packages:

linux-image-686-pae
linux-headers-686-pae

https://help.ubuntu.com/community/MetaPackages

Kernel Metapackages

These metapackages install the latest linux kernel and modules through a series of dependencies. These make upgrading the kernel much easier, and safer, since they ensure that all required modules and headers are also installed.

• linux-generic: Always depends on the latest generic Linux kernel available.

• linux-headers-generic: This package always depends on the latest generic kernel headers available.

• linux-image-generic: This package always depends on the latest generic kernel image available.

• linux-restricted-modules-generic: This package always depends on the latest restricted modules available for generic kernels.

I'm thinking that maybe when the 3.1 kernel failed to install, it may have been due to not having the meta packages installed for whatever reason. So the question is, are those meta packages essential, or just highly recommended?

Thanks

[kruijf]

I got the: linux-image-486 should i install the: linux-image-3.2.0-1-686-pae ??

[Chris M]

I would be surprised if your computer can't handle the PAE kernel, but not knowing (or remembering) what your hardware is, you can check it out: http://en.wikipedia.org/wiki/NX_bit#Linux

Assuming you have a relatively new processor, I would. The 486 was a default install to deal with those with super-old computers. I'm pretty sure the 486 kernel only utilizes 1 core, so if you have multiple cores, I would absolutely do it.

Here's what I have installed:

linux-image-3.2.0-1-686-pae
linux-headers-3.2.0-1-686-pae
linux-headers-3.2.0-1-common
linux-image-686-pae
linux-headers-686-pae
linux-kbuild-3.2

I think you have Intel everything, and the Intel video driver is imbedded in the kernel, so this might fix you up.

[kruijf]

My system have a intel i3 processor Intel hd graphics and 4GB memory.

[viking777]

I only just noticed this, but subsequent to the 3.2 kernel upgrade I had to reinstall the virtualbox-dkms package to get vbox to work again.

[Mr. B]

My system have a intel i3 processor Intel hd graphics and 4GB memory.

Sounds more like a 64bit machine.

[kruijf]

My system have a intel i3 processor Intel hd graphics and 4GB memory.

Sounds more like a 64bit machine.

the problem is whit 32 and 64 bit.

[Chris M]

My system have a intel i3 processor Intel hd graphics and 4GB memory.

Sounds more like a 64bit machine.

It is. If it were me, I'd go 64-bit.

kruijf, I'm assuming the 486 to 686 upgrade didn't work. There are two things you can try. Install the latest Google Chrome and see if you have a problem. Chrome embeds flash.

Then, you can try to smxi-sgfxi install the video driver.

The only time your flash issue has been a problem for me is on my Intel graphics laptop. It drove me nuts. The only thing that fixed it was the kernel upgrade. But at this point, I'd consider sgfxi.

Also, make sure your BIOS is up to date.

Good luck.