CrunchBang Linux

ivanovnegro

Ivan #000000

From: unstable madness

Registered: 2011-06-02

Posts: 5,324

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

^ +1. If you have no issues, leave as is.

---

If you do not like it... roast your own! 

MPD | mplayer | Firefox | fonts

Narvey

Member

Registered: 2011-09-26

Posts: 25

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

Waldorf issue: annoying
The battery meter doesn't show up in the system tray, even though it is in autostart.

Solution:
Add the following line after the lines about starting the volumeicon:

## Enable power management AFTER volume
(sleep 30s && xfce4-power-manager) & 

And remove the original xfce4-power-manager entry

Last edited by Narvey (2012-08-17 18:31:52)

capoassurdo

Member

Registered: 2012-05-02

Posts: 10

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

Waldorf: Catalyst 12.6 and Xorg 1.13 aren't friends

Solution:

1. Add these repos to downgrade Xorg

deb http://snapshot.debian.org/archive/debian/20120515T220710Z/ wheezy main
deb-src http://snapshot.debian.org/archive/debian/20120515T220710Z/ wheezy main

2. Create the file /etc/apt/preferences.d/60xorg_rollback.pref

Package: xserver-xorg*
Pin: origin "snapshot.debian.org"
Pin-Priority: 1001

3. In order to prevent apt check the date in the repos (this mechanism prevents accidental installation of older software), we create a file called /etc/apt/apt.conf.d/60ignore_repo_date_check

Acquire
{
Check-Valid-Until "false";
}

4- We make the changes and downgrade xserver-xorg package

as root:

# apt-get update
# apt-get dist-upgrade

5. Install AMD Catalyst 12.6

fonte: http://lists.debian.org/debian-user/201 … 00647.html

Last edited by capoassurdo (2012-10-31 13:16:10)

Blackout

Member

Registered: 2010-12-16

Posts: 28

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

On sony vaio notebooks
taping the touchpad doesn't work

solution in the autostart replace the egrep command with the following:

if egrep -iq 'Sony Vaio Jogdial' /proc/bus/input/devices; then
    synclient VertEdgeScroll=1 &
    synclient TapButton1=1 &
fi

pvsage

Internal Affairs

From: North Carolina

Registered: 2009-10-18

Posts: 9,251

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

@Blackout:  Is this after a migration from Statler to Wheezy/Waldorf or Sid, or is this on a clean Waldorf install?  If the latter, I can fork this to the Development area.

---

while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.

Blackout

Member

Registered: 2010-12-16

Posts: 28

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

after a clean install ans also after upgrade to testing and also to sid

Last edited by Blackout (2013-05-25 13:03:39)

mcred

New Member

Registered: 2013-05-28

Posts: 2

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

On sony vaio notebooks
taping the touchpad doesn't work

solution in the autostart replace the egrep command with the following:

if egrep -iq 'Sony Vaio Jogdial' /proc/bus/input/devices; then
    synclient VertEdgeScroll=1 &
    synclient TapButton1=1 &
fi

Thank you for the idea to solve my touchpad problem, as I also had a touchpad whose tapping didn't work.

The code for my new Waldorf install was the same as above, but had the generic 'touchpad' instead. My touchpad is
a Alps PS/2 ALPS GlidePad according to "/proc/bus/input/devices". Made the change, now tapping works.

Thanks again!

Tengukami

New Member

From: Iceland

Registered: 2013-02-19

Posts: 4

Re: Statler^Wheezy / Statler^Sid - known issues *with solutions*

Hi, can someone tell me why I turned on my computer this afternoon and found that Waldorf has just straight-up refused to connect to any wireless network at all?

OK, to be more specific: I get a lot of messages about Emask, "FPDMA QUEUED" errors, and failing to read DMA on start up. Wireless networks display but do not connect. Other stuff, like the browser or terminal, will not load at all.

Currently using a Live USB to post. My hard drive is fine - I can access it without trouble, and everything on it works. I'm currently Googling around looking for a solution, but any tips from the community would help. Thanks.

EDIT: lol no it's the motherboard. Trying to install on a new HDD resulted in GRUB being unable to write to the disk. Guess I'll be picking up a new machine, thanks all the same.

Last edited by Tengukami (2013-06-02 01:31:16)