i have the same adapter not found errors with 0.21b, the older a version worked fine.
Works only on 1 machine, couple others does not work.
Also on top of that, if i do not have monitor plugged in while booting, when i plug it in it complains "Video mode not supported", meaning it's running resolution beyond the tiny old Dell LCD i'm using.
So i'm mostly running the older version as the newer version does not work at all for me.
Trying the above mentioned ->
http://developer.amd.com/sdks/amdappsdk/assets/ati_stream_sdk_installation_notes.pdf section 2.2
EDIT: Typing all kinds of special characters on US keymap wasn't my idea of fun, it's just easier to use old version or roll my own in the next upcoming weeks than fool around with something obviously broken.
Why are you plugging in a monitor after booting ?
http://developer.amd.com/sdks/amdappsdk/assets/ati_stream_sdk_installation_notes.pdf section 2.2 refers to you accepting the license agreement. You can do this manually or click the handy little icon in system called ATI license agreement. Also how is something broken because you have to change the keymap to suit your liking ? Sorry but bad workman blames his tools springs to mind
I did accept the SDK -.- I tried from terminal, and from system, and as a regular user etc.
and keymap has nothing to do with being broken. Being broken has everything to do with the drivers not working anymore. There are also other minor bugs and glitches which are annoyances.
Also a bad workman is someone who does not recognize when tools are broken, or does not recognize when a better one is required.
Plugging monitor after booting -> when you boot up say 5 machines from cold, are YOU going to wait for one to boot up individually, or power up all at the sametime?
Or if you meant "why would you need monitor after booting up", maybe starting the miner and verifying clocks. Didn't intend to just idle those machines.
aticonfig can see the adapters, but not phoenix, or amdoverdrivectrl etc. complains lack of ATI drivers. i used aticonfig initialize, but that is to no avail -> restarting X causes only a black screen, won't come back.
I would call that broken, when out of box advertised features do not work, not even after sensible amount of research & trying, whereas a older tool works as expected
Btw, Ad hominem is an argumentation mistake, quite an serious one.
I'm not starting an argument just pointing out that you didn't post anything about your hardware or what you are doing you just picked things out and posted complaining about them. How am I meant to make linuxcoin better if everyone just posted "it don't work" ?
You screen won't work after you boot because the configuration is generated on the fly but can be set in the xorg configuration file. If you was a competent linux user you would know this and edit your configuration files accordingly. But no you come here to say it don't work without asking anyone about the issues you was having. I reiterate a bad workman always blames his tools.
If you have a question or a problem with linuxcoin then ask away there are lots of helpful people here that give up their time for free to help people out. What I'm not interested in is people posting rants on this thread moaning about broken machines and not posting anything
usefulThis isn't a linuxcoin issue it's just how the drivers work. why can't you just VNC into the machines ?.
What GPU's are you using that doesn't work ? There is a bug with how the configuration file is generated. This is fixed in the final version. If this is affecting you and your persistent you can copy and paste the following intoetc/init.d/fglrx
#!bin/sh
#etc/init.d/fglrx
#
### BEGIN INIT INFO
# Provides: fglrx
# Required-Start: $all
# Required-Stop: $all
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/stop fglrx
# Description: Start/stop fglrx
### END INIT INFO
case "$1" in
start)
echo "Configuring fglrx."
if [ -fetc/X11/xorg.conf ]; then
echo "Configuration found !! Skipping."
else
aticonfig --initial -f --adapter=all # Configure GPGPU
fi
;;
stop)
echo "Cleaning up fglrx configuration"
# not used in this version !!
;;
*)
echo "Usage:etc/init.d/fglrx {start|stop}"
exit 1
;;
esac
exit 0
and reboot. If anyone is having problems with linuxcoin don't just post it don't work. Post as much information about your system as possible and any error messages. sorry if i'm blunt you've caught me on a bad day
Now you are trying to just annoy me.
"If you was a competent linux user you would know this and edit your configuration files accordingly.". I do admit i don't use it on desktop - because it sucks as desktop if you need to get work done, but that is quite an insult. I probably have 100x the experience you do (I do happen to manage hundreds of servers).
Systems in question which i've tried:
ASUS P5LD2SE Mobo
Celeron 2.66Ghz CPU
1Gb DDR2 667
PowerColor HD5830
Kingston USB Stick for boot
Another System:
ABIT IN9 mobo (their flagship before they went bust)
Core2Duo X6800 (yes, extreme series a bit overkill for this)
4x1Gb DDR2 667
2xClub3D HD5870
Kingston USB Stick for boot
One did work, but i can't recall the specs of the machine anymore. Very similar to those tho.
Catalyst etc. complains lack of drivers.
aticonfig init makes new xorg.conf, but then X won't start up.
Persistence does not seem work, used unetbooting to create the sticks, and specified ~1Gb for persistence. Hasn't mattered tho so far that much i've been arsed to look into it.
This isn't a linuxcoin issue it's just how the drivers work. It is VERY much Linuxcoin issue, if newer Linuxcoin does not work but older does. Simple as that, doesn't require a genius to understand.
why can't you just VNC into the machines ?. So linuxcoin has VNC setup out of the box? Tbh, i did not bother to take a look if it were, i did not see NX or VNC references in any obvious places.
now am I meant to make linuxcoin better if everyone just posted "it don't work" ?I did reference earlier discussion about this very same problem, on the previous page someone else was having similar problems.
What I'm not interested in is people posting rants on this thread moaning about broken machines and not posting anything usefulThose machines work perfectly, ty for asking. It's linuxcoin which does not.
I reiterate a bad workman always blames his tools. So it's my fault that LinuxCoin has bugs?
What does it say about developer who always blames users "it can't be a bug! i created it so it's bug free, it's your fault for not putting effort work around the 'features'!"
Lol you annoyed me of as soon as you opened you mouth ! Hmm so you you manage all these servers but didn't think to post you xorg.conf file ? And please tell me more about this desktop you talk about that sucks so much ? You mean you run headless ? If you manage all these servers you should know that there's no need for a screen unless you want to connect your machines wireless and need to enter a key before you can get an IP address. You should check out the following link.
http://www.linuxcoin.co.uk/wiki/index.php/SSH_X11forwardingYou might also like
http://www.linuxcoin.co.uk/wiki/index.php/SettingupVNCremotelyAs I said the bug is
NOT with the drivers but
WITH the initialization script. My fault ? yes, someone with hundreds of linux servers under his control failed to notice ? I feel sorry for your boss
I bet if you check now you will see that your actually running on the free radeon drivers. If you want to check
catetc/X11/xorg.conf | grep fglrx
If you see anything return then you have the fglrx drivers loaded. If not your running on the free radeon driver and in that case you need to do.
sudo rmetc/X11/xorg.conf
sudo aticonfig --initial -f --adapter=all
sudoetc/init.d/gdm stop
When you see the terminal
sudoetc/init.d/gdm start
everything should work as expected.
If you actually RTFM for unetbootin you will see that it specifies that the persistence option is
ONLY for ubuntu. Not a linuxcoin issue and someone as competent as you should already know this lol The reason why is ubuntu looks for partitions called casper-rw. Linuxcoin looks for live-rw. If you want persistence go over to linuxcoin and download a persistence file like specified in the OP. if not a systems engineer with hundreds of servers under your control like yourself should be able to manage.
dd if=/dev/zero of=/path/to/usb/live-rw bs=1M count=<your_size>
mkfs.ext4path/to/usb/live-rw
And reboot.
You screen issues can be fixed by hitting CTRL + ALT + F1 and editing your xorg.conf to reflect your monitor or use xrandr. If you manage to get the fglrx drivers to auto detect on the fly then I would like to know about it as I'm sure lots of others will.
xrandr --auto
Expecting a
ALPHA build to be bug free is insane
The bug with the initialization has been fixed and you have been offered a solution. And as for your comments on you couldn't be arsed to do this and that lol A bad workman always blames his tools. The heart of your problems are in you posts. Comments like
did not bother to take a look if it were
and
tho so far that much i've been arsed to look into it
show's you do not research your issues and just assume it doesn't work. So I suggest you roll you own with your overwhelming wealth of knowledge and release it to the public lol I will look forward to trying it out.
