1 |
Walter Dnes wrote: |
2 |
> I've set up Dosbox to run old DOS games, and even managed to load |
3 |
> Windows3.1 under it. The emulation is perfect... Chessmaster 3000 whups |
4 |
> the daylights out of me just like in the old days. Anyhow, I had built |
5 |
> the virmidi module to provide midi support to some of the games. In |
6 |
> /etc/conf.d/local.start I had the line... |
7 |
> |
8 |
> modprobe snd-virmidi index=1 |
9 |
> |
10 |
> It worked fine... until I updated the kernel. I copied over my |
11 |
> previous .config and ran "make oldconfig", so the module should still be |
12 |
> getting built. At bootup, I now get... |
13 |
> |
14 |
> * Starting sshd ... [ ok ] * Starting local ... |
15 |
> FATAL: Error inserting snd_virmidi (/lib/modules/2.6.12-gentoo-r4/kernel/sound/drivers/snd-virmidi.ko): No such device |
16 |
> * Failed to start local [ !! ] |
17 |
> |
18 |
> dmesg contains the following... |
19 |
> |
20 |
> ReiserFS: hda6: checking transaction log (hda6) |
21 |
> ReiserFS: hda6: Using r5 hash to sort names |
22 |
> snd_rawmidi: Unknown symbol snd_seq_device_new |
23 |
> snd_mpu401_uart: Unknown symbol snd_rawmidi_receive |
24 |
> snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack |
25 |
> snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek |
26 |
> snd_mpu401_uart: Unknown symbol snd_rawmidi_new |
27 |
> snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops |
28 |
> snd_opl3_lib: Unknown symbol snd_seq_device_new |
29 |
> snd_ymfpci: Unknown symbol snd_opl3_create |
30 |
> snd_ymfpci: Unknown symbol snd_mpu401_uart_interrupt |
31 |
> snd_ymfpci: Unknown symbol snd_mpu401_uart_new |
32 |
> snd_ymfpci: Unknown symbol snd_opl3_hwdep_new |
33 |
> ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ |
34 |
> 9 |
35 |
> 0000:00:0f.0: tulip_stop_rxtx() failed |
36 |
> eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. |
37 |
> Card-VirMIDI #1 not found or device busy |
38 |
> Card-VirMIDI soundcard not found or device busy |
39 |
> |
40 |
> Any ideas? |
41 |
> |
42 |
|
43 |
Why are you loading the module in local.start? Normally that is done by the alsasound service. You should probably go through the alsa guide and make sure you've done everything there: http://www.gentoo.org/doc/en/alsa-guide.xml You can use the alsa-driver ebuild to rebuild your alsa drivers if necessary. |
44 |
|
45 |
Zac |
46 |
-- |
47 |
gentoo-user@g.o mailing list |