At Thu, 23 Jan 2003 04:34:44 +1100, julian wrote: > > hi, > > i realise you are a very busy guy, but several people have recommended i talk to you >about my /dev/snd problem because they have not been able to solve it or understand >why it is happening. if you ever have time i would be most grateful if you could look >over it. > > cheers, > > julian oliver > melbourne australia. > > > > Begin forwarded message: > > Date: Wed, 22 Jan 2003 06:24:54 +1100 > From: delire <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [Alsa-user] // /dev/snd disappears on restart... what's going on? // > > > hi, i have a strange problem on a new laptop, where with the alsa device directory >mysteriously disappears on reboot. this has happened to me before on another dell >laptop. this is a fresh install of debian unstable. i never got to the bottom of >exactly the same problem on a machine many months ago as i was forced to reinstall, >and that fixed it anyway. > > i built a 2.4.20 kernel to allow me to use the usb-midi device. naturally i had to >make the alsa drivers again so i ran > the './configure --with-cards=maestro3,usb-audio --with-sequencer=yes --with-oss=yes >&& make && make install'. this of course went through fine as it always has. > > however i forgot to run the ./snddevices script and rebooted. after reboot i >realised the error and ran the script. i edited my /etc/modules.conf and restarted >the machine another time to test the drivers. the /dev/snd directory had mysteriously >vanished. i ran the script again and had perfectly working drivers, midi and all [i >have setup alsa many times on several systems]. however on reboot, the /dev/snd >directory disappears again and again, forcing me to manually run the script. i have >three other alsa machines, all of which run alsa normally. > > if anyone has and ideas as to this weirdness let me know by replying direct as i'm >sick of running the damn script on restart! > > i guess i can manually make the symlinks, but i want to understand what's going on >first..
sorry, i have no idea, too. it's really weird. one sure thing is that the ALSA driver, ALSA lib and the (standard) alsasound initscript never touch this. the culprit must be in different places. i'm not familiar with a debian system. is there any service to check the unauthorized files invoked periodically via cron? and which initscript is used on debian? i saw both "alsa" and "alsasound". also, try to reboot the machin without plugging the usb device. any changes? if yes, then this has something to do with the hotplug stuff. ciao, Takashi ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
