You are not logged in.
Pages: 1
I had been having lots of issues with my system after being on vacation for 2 weeks and coming back and being bomabarded with updates, and finding that I now had Duke rather than Voodoo. So I did I new install of Duke and everything is good so far...except when I put in an SD card or connect my digital camera it doesnt seem to be rceognized as I cant access it. It doesnt appear on the desktop, or anywhere for that matter. Being that Im still fairly new to Linux Im not sure whats up. Im assuming I need to install drivers of some sort, but Ive searched docs all night and havent found what it would be. Does anyone know if I need to install drivers, and if so what they are, and if not what might the problem be? Thanks..Im sure this is a newbie kind of question, but I appreciate the help
"The hardest thing is rendering a moment moving to fast to endure"
Offline
Have you read this?
My guess is that that should get it running...
Stand back, intruder, or i'll blast you out of space! I am Klixon and I don't want any dealings with you human lifeforms. I'm a cyborg!
Offline
AHA...thanks man....the problem was dbus wasnt starting because of this file.../var/run/dbus.pid...so I just had to remove that and start hal because I didnt have it in my daemons list. Thanks again...this was my first time installing Arch on my own, I guess a few things got overlooked
"The hardest thing is rendering a moment moving to fast to endure"
Offline
Hello - I have the same problem starting with Duke. I also had to manually delete /var/run/dbus.pid
My question would be, however, how come that file isn't always automatically deleted by dbus on exit? Because, from time to time, I get a [FAIL] from dbus at startup, because of this file. (after a clean shutdown, of course)
Offline
I dunno man. But Ive had issues with dbus starting on DUke still...and hal. Sometimes I have start them manually and sometimes I end up having to reboot to get them to work.
"The hardest thing is rendering a moment moving to fast to endure"
Offline
If you start hal, then it starts dbus. So if you have both hal and dbus in your list, then you try to run dbus again. But the daemon finds the pid file of the first instance. So there is no need for both dbus and hal. Only hal.
Offline
ahhhh...ok. That might be my problem then. Because I do have both hal and dbus in my daemons
"The hardest thing is rendering a moment moving to fast to endure"
Offline
Pages: 1