Hello!

I've upgraded from Fedora Core 1 to Fedora Core 2, and after lots of fiddling around (and reading!) I still can't figure out why 1) my volume settings are no longer remembered (I use alsa) 2) my joystick no longer works 3) gkrellm no longer detects my sensors and 4) how to get rid of the ac, battery, and other laptop modules that were installed that I don't need because my computer's not a laptop. And these are only the problems I can think of off the top of my head right now. I was getting pretty good at getting stuff to work before Fedora Core 2... I'm a little frustrated with all of the changes. Is it something simple I've over looked or do I have to re-learn a bunch of stuff? (If it's the latter, I might try a new distro.)

Thanks,
Ryan

P.S. If you'd like to see my modules.conf & modprobe.conf files or any other specific info, let me know.

Because you no longer have the alsa script which runs alsactrl store at shutdown and alsactrl restore at startup running at your boot or default runlevel. While the ALSA drivers are integrated into the kernel with the 2.6 series, alsa-libs and alsa-utils are not, and your previously-installed versions may not conform to the driver version installed by the kernel. You might want to re-install ALSA from the site (in which case you only need install alsa-libs and alsa-utils), or reinstall ALSA from a FC2 RPM.

Don't use Fedora, so can't tell you exact procedure (or the precise name of the script), once you have alsa-utils again available to provide alsactrl, but I would start looking in /etc/rc.d area for "alsa", or "alsasound" or something similar. Adding the script, once found, to the boot or default runlevel is left as an exercise for actual Fedora Core users .

a) Joystick not compiled into the kernel or as a module; b) if compiled, module is not requested to load via /etc/modprobe.conf or entries in /etc/modules.conf were not properly transferred to modprobe.conf when kernel was upgraded from 2.4-series to 2.6.series; c) joystick is not found because sound card's gameport module is not loaded (so the port that the joystick is connected to is not available, so joystick cannot be detected). Again, a kernel configuration issue.

You mean the motherboard sensors? Was support for reading these sensors compiled into the new kernel? If so, are the modules which perform this function loaded? If the data is not being collected, GKrellM can't read it.

Right-click on GKrellM, choose "Configuration" and deactivate the modules you don't want to display.

Well, it may or may not be "simple" but it looks like most of the changes you're experiencing are due to the migration to the 2.6 series kernel. Once you get used to that, you should not have too many problems. It's definitely worth installing the kernel source for your currently-running kernel, and recompiling it once, just to see how things are different, and whether or not you need to enable some things that may no longer be handled the way you were used to.

Hope this helps.

hey motub!

thanks for the reply. i'm just getting back to this stuff now (almost a month later!) because of stupid work.

anyway, i've been goofing around with this stuff and got my joystick to work and my sound settings to be rembembered when i log off. i think the main problem was my modules.conf file wasn't properly converted to the modprobe.conf (i believe that was one of your observations). the following is my modprobe.conf so far. i'm not sure if it contains any errors or redundentcies (sp?) but at least it's working:

---
alias eth0 8139too
alias usb-controller uhci-hcd
alias snd-card-0 snd-ens1371
options snd-ens1371 joystick_port=1 options analog js=auto
install snd-ens1371 /sbin/modprobe -i snd-ens1371;\
/usr/sbin/alsactl restore; \
/sbin/modprobe -iq joydev; \
/sbin/modprobe -iq analog
alias char-major-195 nvidia
install snd-card-0 /sbin/modprobe --ignore-install snd-card-0 && { /usr/sbin/alsactl restore >/dev/null 2>&1 || :; }
remove snd-card-0 { /usr/sbin/alsactl store >/dev/null 2>&1 || :; }; /sbin/modprobe -r --ignore-remove
---

also, i should've have been more clear about the other problems... 1) the sensors for gkrellm i was talking about are the temperature, fan speed, etc. i followed the instructions from "sensor-detect" but it's still not working. and 2) the laptop (and other unneeded) modules i was talking about, like battery, ac, etc. are modules that show up when i enter "lsmod" (see below). these are not related to gkrellm (i don't think) as i may have led you to believe in my last post. my problem is, i don't know how to prevent them from loading.

---
Module Size Used by
i2c_dev 6784 0
snd_mixer_oss 13824 2
analog 8608 0
joydev 6976 0
snd_ens1371 17380 2
snd_rawmidi 17444 1 snd_ens1371
snd_seq_device 6152 1 snd_rawmidi
snd_pcm 69256 1 snd_ens1371
snd_page_alloc 8072 1 snd_pcm
snd_timer 17284 1 snd_pcm
snd_ac97_codec 54788 1 snd_ens1371
snd 39396 7 snd_mixer_oss,snd_ens1371,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer,snd_ac97_codec
gameport 3328 2 analog,snd_ens1371
soundcore 6112 3 snd
via686a 14728 0
eeprom 6024 0
i2c_sensor 2176 2 via686a,eeprom
i2c_isa 1792 0
i2c_viapro 5516 0
i2c_core 16660 6 i2c_dev,via686a,eeprom,i2c_sensor,i2c_isa,i2c_viapro
binfmt_misc 7176 1
parport_pc 19392 1
lp 8236 0
parport 29640 2 parport_pc,lp
autofs4 12932 0
8139too 17920 0
mii 3584 1 8139too
floppy 47440 0
sg 27680 0
scsi_mod 91984 1 sg
nls_cp437 5376 2
vfat 9984 2
fat 33600 1 vfat
nls_utf8 1536 3
ntfs 98160 1
dm_mod 32800 0
uhci_hcd 24472 0
button 4632 0
battery 6924 0
asus_acpi 8984 0
ac 3340 0
nvidia 4817332 12
ipv6 184672 24
ext3 103656 2
jbd 40728 1 ext3
---

if you can think of anything that's obvious, let me know. if you need more details, i'll try to get them to you sooner than later (stupid work!).

thanks,
ryan