Many devices missing in /dev inc snd dsp and all fdout

lilsirecho · 2004-02-14 03:28:02

No sound and /dev/snd.../ dev/dsp... among many others.

Is there a package missing from the system?

sarah31 · 2004-02-14 05:35:02

well that depends. if you use alsa you have to have the alsa packages installed (unless you are using the 2.6.2 kernel). then you have to make sure you are loading your modules and have the proper entries in your devfsd.conf

there an OVERWHELMING number of posts to thei forum regarding sound please search and read.

rasat · 2004-02-14 05:56:49

The "News, FAQ & LP" topic on this forum, may answer some of your questions:
http://bbs.archlinux.org/viewtopic.php?t=2250

lilsirecho · 2004-02-14 17:12:20

Sarah;

Thanks for the response.

I assure you I have searched the whole of forums identified with the sound problems encountered. I would not start a new post if I had not exhausted the material.

I have encountered :
REGISTER ^ sound....et cetera
REGISTER ^snd...et cetera
and as an alternative....
REGISTER sound...etcetera
REGISTER snd.... et cetera

I tried them both!!!

I have entered the long list of ... aliases..more than once!!!
I probably have more entries into various files as suggested by posts that probably need to cleared out.

The significant thing I found by comparing this upgrade with the previous arch 2.4.21-1 was the missing files from /root/dev. The number missing is probably 200 and the significant directories missing are /dev /snd and /dev/sound.

Searching the forum for pertinent information concerning those particular files showed no reference to them. I do not know how they are created. I suspect they weren't properly upgraded when I upgraded to 2.4.24-1.

I am aware of the procedures extant for alsa and its relevant data entries but my post refers to the missing files in /root/dev which by comparison with arch 2.4.21-1 number in the hundreds.

I hope you understand my question better.

Xentac · 2004-02-14 17:27:55

uname -a

Make user you are actually running 2.4.24.

depmod -a

Then try rebooting. The reason those devices aren't on your filesystem is because your modules are loaded. To see which modules are loaded type 'lsmod'.

lilsirecho · 2004-02-14 17:31:05

Rasat;

Thanks for response. I have looked at the references and find the same instructions that I have utilized over and over.

The reference to REGISTER differences was encountered again(of course); its either one or the other(or both). It is not apparent which may or may not be correct but it is apparent to the user that if a typo occurs the entry is useless. The computer is unforgiveable. Therefore type exactly what is listed, right or wrong!

When I upgraded to 2.4.24-1 the instructions said;
Remove all kde pkgs but not their dependencies......

Reading this, I removed all kde identified pkgs......

I ended up in a big mess with the upgrade because I didn't include arts and koffice...they are part of kdesystem but do not have kdepkg ID's.

A better statement would have been to include arts and koffice along with the kde pkgs. Its possible there is more I haven't yet realized!!!!

I try very hard to do exactly what is listed because I know it is important to do the right thing.

However, what I need to know, for now and for later on when things go bad again, what belongs in /root/dev and how does it get installed?

lilsirecho · 2004-02-14 17:51:59

Xentac;
Entered pacman -Q |less
Result: kernel 2.4.21-2

Entered : cd /var/cache/pacman/pkg
entered: ls -l |less
Result: kernel 2.4.24-1
kdepkgs 3.2.0
Obviously the download via pacman -Syu did not work, again!

I swear the last time I looked at the cache it had kernel 2.4.21-1 in it and the -Q listed kernel 2.4.21-2.
In order to complete the download of the upgrade which was held up by koffice conflict I entered pacman.conf to ignore koffice and kernel. The upgrade of the remaining pkgs ensued(150 or so).

Now, the cache shows the upgrade kernel!!!!!!!

I assume I should pacman -S kernel now.

lilsirecho · 2004-02-14 18:45:43

Xentac;

I entered: Pacman -S kernel
Waited while it completed...
Entered : pacman -Q |less
Result: kernel 2.4.24-1 listed
Entered: uname -a
Result: kernel 2.4.21

:?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?:

lilsirecho · 2004-02-14 19:27:38

Gents:

Entered pacman -S kernel
Kernel entry completed

After reboot command ; boot : 2archEBDA is big; setup stack overlaps LILO second stage...... blinking cursor displayed....no computer activity...waited ten minutes..
Now in windows and have no arch boot in 2.4.24-1 or whatever is present in the drive.

Is there a way out?

Mr Green · 2004-02-14 19:46:48

Ouch did you lilo after upgrading kernel......?

Mr Green

lilsirecho · 2004-02-14 20:03:24

I did not lilo after upgrading kernel.

There is no place wherein it says to do so. Pacman -Syu is all that is stated for an upgrade. I can well assume an upgrade also upgrades every requirement to do so including lilo. There is no reason not to make such an assumption.

All of the procedures require that the user be an expert in "arch language" which is cursory and 'generalized". No wonder I get into trouble!

I have seen posts which omit...thats right......omit the step.... /sbin/lilo....that's understood!!!!!! Yeah right!!!!

I wonder if I can use my old arch CD to get into /sbin/lilo?
Please advise if I can fix this or start over.

Mr Green · 2004-02-14 20:13:01

Yes I do not see why not...

6.7 in install docs tells you how ......

Take a look :-)

Mr Green

lilsirecho · 2004-02-14 20:29:32

Another generalization; install docs 6.7

Dunno where they are!!

lilsirecho · 2004-02-14 21:58:26

Tried the use of arch CD ; vmlinuz root=/dev/discs/disc0/part3
Result ....kernel panic...append a correct root boot option

Segway to arch install prompt: #mkdir /mnt/tmp
#mount /dev/discs/disc0/part3 /mnt/tmp
Result; no such file or directory.

Retried all three times...same results.

Mr Green · 2004-02-15 09:30:55

No my friend you mis understand me.....

Look Here :
[url]http://www.archlinux.org/docs/en/guide/ … 0000000000
[/url]

It will show you how to get back into your box .....

Mr Green

lilsirecho · 2004-02-15 17:54:36

Performed the procedure outlined probably 15 times with the result always the same....no such file or directory. I was familiar with the method and performed it as I said probably 15 times with reboots.

Conclusion: wiped the info from disc.

I am re-installing.

Xentac · 2004-02-15 18:08:04

This time, just install a base system off the cd and then install everything off the internet after updating the base system. You'll have less upgrade problems, because you won't be upgrading, you'll be installing.

lilsirecho · 2004-02-16 08:32:33

Xentac;

That I did and had no problems . The ship is not sinking anymore.
The rats have deserted the ship!!!

When is a zero always equal to a one?

Arch Linux

#1 2004-02-14 03:28:02

Many devices missing in /dev inc snd dsp and all fdout

#2 2004-02-14 05:35:02

Re: Many devices missing in /dev inc snd dsp and all fdout

#3 2004-02-14 05:56:49

Re: Many devices missing in /dev inc snd dsp and all fdout

#4 2004-02-14 17:12:20

Re: Many devices missing in /dev inc snd dsp and all fdout

#5 2004-02-14 17:27:55

Re: Many devices missing in /dev inc snd dsp and all fdout

#6 2004-02-14 17:31:05

Re: Many devices missing in /dev inc snd dsp and all fdout

#7 2004-02-14 17:51:59

Re: Many devices missing in /dev inc snd dsp and all fdout

#8 2004-02-14 18:45:43

Re: Many devices missing in /dev inc snd dsp and all fdout

#9 2004-02-14 19:27:38

Re: Many devices missing in /dev inc snd dsp and all fdout

#10 2004-02-14 19:46:48

Re: Many devices missing in /dev inc snd dsp and all fdout

#11 2004-02-14 20:03:24

Re: Many devices missing in /dev inc snd dsp and all fdout

#12 2004-02-14 20:13:01

Re: Many devices missing in /dev inc snd dsp and all fdout

#13 2004-02-14 20:29:32

Re: Many devices missing in /dev inc snd dsp and all fdout

#14 2004-02-14 21:58:26

Re: Many devices missing in /dev inc snd dsp and all fdout

#15 2004-02-15 09:30:55

Re: Many devices missing in /dev inc snd dsp and all fdout

#16 2004-02-15 17:54:36

Re: Many devices missing in /dev inc snd dsp and all fdout

#17 2004-02-15 18:08:04

Re: Many devices missing in /dev inc snd dsp and all fdout

#18 2004-02-16 08:32:33

Re: Many devices missing in /dev inc snd dsp and all fdout

Board footer