I finally got ampache running on my server after the update to openSUSE 12.1 borked it.

All thanks to this post on the ampache forum.

I've also set up...

owncloud 2.0.1
eyeos 2.5
oneye
zoneminder
punbb

On there too.

Cheers,

T

Hi all,

My Screen name comes from my job (Yeah, I know sad really)
I'm a Logistics Coordinator for one of the bonded warehouses at LHR (Heathrow airport)
But our office often gets referred to as "System Control" and us as Controllers.

My avatar is just my name as a qr code.

Cheers,

T

Hey all,

After a brief hiatus I'm back with #!

Here's all three desktops from my laptop.

1: The latest and greatest #!
2: Fedora 16 with gnome 3.2
3: Some obscure and rarely used OS that came with the lappy.

http://flickerluke.co.uk/pics/fedora/all_three1_small.jpg

You gotta love choices. smile

Cheers,

T

4

(8 replies, posted in Help & Support (Stable))

Just a tip though,

With this driver any kernel updates will require you to re-run some of the installation commands.

On wheezy I have to run..

m-a a-i broadcom-sta

and

modprobe wl

every time the liquorix kernel is updated to get the wireless up and running.

5

(8 replies, posted in Help & Support (Stable))

Yeah, it seems by default using that driver assigns eth1 to the chip.

I've not noticed any problem or issues with it though.

*edit* My iwconfig output is identical to yours too.

6

(8 replies, posted in Help & Support (Stable))

Is yours a broadcom chip?

Did you install the broadcom wl driver

It looks from your iwconfig output that your wireless device has been named eth1.

It's the same on mine using that driver.

http://flickerluke.co.uk/pics/wl.png

Have you tried the nuclear option?

Good old dd

I had a pretty much identical problem with a stick and ended up using...

dd if=/dev/zero of=/dev/sdX

(Replace the X with whatever the stick is on your system)

This will zero write the entire drive wiping everything and then (hopefully) you should be able to create a new partition table and file system.

Just be VERY sure of the dd command before you hit enter as if you mix up the if and of or point it to the wrong partition it WILL eat your system.

Hi there,

There's a post over on the debian forums about this problem with a couple of workarounds.

http://forums.debian.net/viewtopic.php?f=6&t=64174

Might be worth a try.

Cheers,

T

Looks like Omploader itself is down.

http://www.downornot.com/omploader.org

Hey all,

Check out this interview on the 'This week in debian' podcast with our very own corenominal.

http://frostbitemedia.libsyn.com/this-w … isode-26-1

I'm listening to it now, it's got some interesting insights into how and why Philip puts #! together.

cheers,

T

Are you just trying to connect via ssh?

If that's the case then I'd simply ssh into the desktop and then ssh from there into the server.
(Edit: I'd strongly recommend changing the port number used for ssh to something unused higher up the range and it'll need to be forwarded to the machine in question on your router.)

If you need any other services then I'd recommend setting up a dyndns account for the server and forward the ports you need directly to it.

12

(1 replies, posted in Help & Support (Stable))

Hello there, and welcome to the forums.

There definitely seems to be a bit of difficulty with debian based distro's and multiple sound cards.

See if this post can point you in the right direction.

Cheers,

T

I stumbled across this a little while ago.

Couldn't get it out of my head and ended up buying the album from his site.

It's pretty much been on  repeat ever since.

Awesome talent.

Hey CrunchKvg,

As chromium suggested have a look at that thread.

http://crunchbanglinux.org/forums/topic … ult-mixer/

My last post there explains how I permanently set a particular sound device as the default.

Cheers,

T

My problem wasn't exactly the same as yours but my solution may help.

I have a set of external USB speakers permanently plugged into my laptop but was having a hell of a job getting them set as the default sound device.

I followed some advice to create up a .asoundrc file but the sound cards would randomly switch between the two when I booted.

The solution I stumbled on was to edit /etc/modprobe.d/alsabase.conf

The last line was...

options snd-usb-audio index=-2

Which I edited to

options snd-usb-audio index=0

and added a line underneath

options snd-hda-intel index=-2

From what I can see the index=-2 part stops the quoted device from being selected as the primary card.

If you know the device names then hopefully you will be able to apply this to your setup.

16

(527 replies, posted in Artwork & Screenshots)

Just had to post this wallpaper I found on gnome-look here

http://flickerluke.co.uk/pics/ss/crunchbang/jpg2/desk-clean_small.jpg

Everything else is pretty much the same as the past few months.
(It ain't broke so I'm not fixing it smile )

http://flickerluke.co.uk/pics/ss/crunchbang/jpg2/desk-dirty_small.jpg

Cheers,

T

17

(18 replies, posted in Help & Support (Stable))

corenominal wrote:

Bug confirmed, although I have never come across it before. hmm

Should I upload an updated package to the Statler repository?

Yes please, if it's not too much trouble.

I too hadn't come across this bug until I found this topic and thought I'd try it.

I didn't realise it'd kill X and take me all the way back to the GDM screen.

Good thing I'd decided to save the files I was working on first.

18

(26 replies, posted in CrunchBang Talk)

AwesomeFist wrote:

Crunchbang, it's as stable as a chicken's head.
http://www.youtube.com/watch?v=sXUeO3auRZg

I'm almost afraid to ask, but...

What exactly were you searching for when you found that? big_smile

If you installed the nvidia drivers from the nvidia site I'm assuming you

sudo sh NVIDIA-XXXXXX

from runlevel 3?

If so then you should be able to boot to runlevel 3 again, cd to the folder it's in and run

sh NVIDIA-XXXXX --uninstall

to remove the driver.

Then hopefully you should be able to

sudo nano /etc/mopbrobe.d/blacklist.conf

and remove the entry for nouveau and reboot.

*edit*

You'll need to remove the /etc/xorg.conf generated by nvidia-xconfig too.

These lines

[    20.069] (WW) NVIDIA(GPU-0): The EDID read for display device CRT-0 is invalid:
[    20.069] (WW) NVIDIA(GPU-0):     unrecognized EDID Header.

And these

    20.084] (WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot compute DPI
[    20.084] (WW) NVIDIA(0):     from CRT-0's EDID.

Are the most likely culprits

From googling around the best advice I can give is to have a look at this page and try and follow the instruction.
(Not for the faint hearted by the look of it)

*Deleted due to cross post providing the info.*

Ah, ok.

Can you run glxinfo in a terminal for us and post the output?
You may need to install mesa-utils first. (I can't remember if it's installed by default)

Also, can you post your xorg.conf here? We can have a look and see if we can see the problem.

*edit for typo*

Hi SnaveZ,

Have you created an xorg.conf file in /etc/X11?

I had to run

sudo nvidia-xconfig

To create the file before my machine would display the correct resolution.

24

(115 replies, posted in Off Topic / General Chat)

I got an upgrade!

http://www.speedtest.net/result/1168022673.png

I moved recently nearer to the exchange.

Not too shabby for UK ADSL.

Hey Speckled,

On my laptop I managed to install the wl driver following instructions from Here using method 1
(I'm assuming your chipset is supported, ymmv obviously)

The only problem I've found so far is the need to re-run some of the commands for each kernel installed and any liquorix updates.
(Steps 4, 6, and 8 while booted into the new/different) kernel)


I've posted Here to ask if anyone had found a workaround but no luck so far.

Cheers,

T