with scsi emulation on i had a bit of a baffling experience - my drive used to be sda with scsi emu on - now it is sr0! took me ages to figure it out! xcdroast finds it as a scsi drive now and is much happier but xine and mplayer don't seem to be able to open /dev/sr0
I set up symlinks in my custom udev rules and added the line that sets up the scsi devfs structure in dev - they all work fine but but i still have the media player prob - help on that one? xine also broke now - i dunno if this is related but i doubt it as if i boot without append hdc=ide-scsi or whatever it should just be the same system right?
]]>hold the phone - do i even need scsi emulation with 2.6 to use my cd-burner? seems not - why isn't this in the wiki? knowledge gap!
nope... well, at least i'm fine without scsi emulation... i think you can check with "cdrecord -dev=ATAPI -scanbus" or something to that effect
]]>i am not using hotplug as i feel the same about the reams of output as rasat and it seems to work ok normally without it!
]]>Walt
]]>I really hate to slow my boot process, though. Now it's only twice as fast as Windows XP
Thanks for clarifying mctavish
Michael Salivar
Just a little bit more information about my situation...
As I said before to solve my problem I had my soundcard driver first in the modules list and the alsamixer script last in the daemons list.
What I didn't mention is that before the alsamixer entry I have the network daemon which takes a *really long time* to complete - I even had to increase the timeout value for it. It takes that long to get an IP from my ISPs DHCP server I guess.
So my point is that if it wasn't for the network taking so long to complete I would probably still have this problem. So it seems that the soundcard module is taking a very long time to register for whatever reason.
I don't know how, but you could try to put some kind of delay before the alsamixer script to see if that helps.
]]>Something I tried since my last post was simply adding the 'alsactl restore' and 'alsactl -F restore' to my rc.local. Both of these had the same effect, so the script definitely isn't at fault.
I'm at a loss, I don't understand why one second during init, after udev and the modules load, the sound card doesn't exist; then the next after I login everything is fine. Hopefully digging through my kernel config will turn something up.
Thank you
Michael Salivar
alsactl: load_State:1134: No soundcards found...
Here's the really strange thing, if I run the script as root, it restores them just fine.
I assure you that my udev.permissions is setup properly for the sound group, and my user is in this group. I've tried running alsaconf for the aliases in modprobe.conf, and I've moved the alsamixer daemon around in the rc.conf (beginning, end, here and there in the middle). I also tried removing hotplug from that list. Since it loads properly when started manually, I also tried starting it from rc.local, but that didn't work either.
Unlike someone earlier in the thread, my volume levels aren't being restored without this script.
Oh, and this is a pure udev environment. I installed from the beta ISO, didn't install devfsd, and didn't compile devfs into my 2.6.8 kernel. Also, this script worked fine with a nearly identical kernel on the same hardware in Arch 0.6, except with devfs.
What are the differences in the init scripts' environments and the command line's that could be causing this?
Please Help!
and thank you for it
Michael Salivar
The only thing that didn't work, was my usbmouse. I created a symlink to /dev/psaux with the name /dev/usbmouse and now I can use my mouse again. Oh... I also have a script that starts the numlock on every tty, and that was broken too, but is fixed now
Sound works, webcam works, network works... is there anything else that I should check?
thanks alot tpowa since i used my own PKGBUILD to build the kernel i forgot to check the abs tree for any new patches and viola - all works thanks again
[edit]
ps.
congrat for the new Arch logo looks great btw
look at the abs tree and you will find the new patches which were introduced in the 2.6.8.1-3 package including the nice logo from damir
]]>and about compiling the kernel sources - which patches should i apply? i use the default arch abs system/.config plus some small changes to suit my hardware to build my kernel, and no cd patches there...
tnx for your time
[edit]
its not realy a big problem - i can execute k3b using root everytime... but its just annoying not knowing what causes this little freak of nature...