4 Jul
2005
4 Jul
'05
1:44 a.m.
Hi all,
I recently upgraded to kernel 2.6.12-2multimedia-386, and I seem to
have killed my perfectly functioning Midisport 2x2. When I launch
seq24, the Midisport outputs no longer appears as options. It seems
that my cheap onboard laptop soundcard has been defaulted to take care
of MIDI. The firmware appears to load successfully, and I've tried
doing $ modprobe snd-seq , but no luck. Any suggestions would be
greatly appreciated... I just got some new gear and was having a great
time sequencing... what bad timing!
Stephen
4 Jul
4 Jul
4:36 a.m.
On 3 July 2005 at 23:44, Stephen Ceresia <chungkingmansions(a)gmail.com> wrote:
I recently upgraded to kernel 2.6.12-2multimedia-386,
and I seem to
have killed my perfectly functioning Midisport 2x2. When I launch
seq24, the Midisport outputs no longer appears as options. It seems
that my cheap onboard laptop soundcard has been defaulted to take care
of MIDI. The firmware appears to load successfully, and I've tried
doing $ modprobe snd-seq , but no luck. Any suggestions would be
greatly appreciated... I just got some new gear and was having a great
time sequencing... what bad timing!
I would think that you could take care of loading the module(s) in
the right order with some combination of /etc/modprobe.conf (likely)
and /etc/modprobe.preload (maybe). I had to do this to get my Delta
1010 to come 2nd behind my Soundblaster card.
What kernel did you upgrade from? Can't you just use lilo or grub to
boot your previous kernel?
G'luck....
--
Kevin
2:37 p.m.
I would think that you could take care of loading the
module(s) in
the right order with some combination of /etc/modprobe.conf (likely)
and /etc/modprobe.preload (maybe). I had to do this to get my Delta
1010 to come 2nd behind my Soundblaster card.
I don't appear to have a modprobe.conf or modprobe.preload file. I'm
guessing this is part of the problem. Is there some way to generate
these files, or can I manually create them? What should they contain?
What kernel did you upgrade from? Can't you just use lilo or grub to
boot your previous kernel?
I upgraded from 2.6.8. I guess I could just boot to the previous one,
but I keep reading about all these great 'realtime' audio features of
2.6.12. :-) Also, I'd like to learn how to fix this problem. The
first time I got my Midisport working, I think it was more luck than
anything else...
6:08 a.m.
Stephen Ceresia wrote:
I recently upgraded to kernel 2.6.12-2multimedia-386,
and I seem to
have killed my perfectly functioning Midisport 2x2. When I launch
seq24, the Midisport outputs no longer appears as options.
What are the output of lsmod and the contents of /etc/modprobe.conf
and /proc/asound/cards?
Regards,
Clemens
7:44 a.m.
Last Monday 04 July 2005 04:44, Stephen Ceresia was like:
I recently upgraded to kernel 2.6.12-2multimedia-386,
and I seem to
have killed my perfectly functioning Midisport 2x2. When I launch
seq24, the Midisport outputs no longer appears as options. It seems
that my cheap onboard laptop soundcard has been defaulted to take care
of MIDI. The firmware appears to load successfully, and I've tried
doing $ modprobe snd-seq , but no luck. Any suggestions would be
greatly appreciated... I just got some new gear and was having a great
time sequencing... what bad timing!
There is now a 2.6.12-3-multimedia-* kernel available from Agnula, the
problems you describe may have been fixed (I don't know). This may also be
due to changes in the ALSA modules (since >= 1.0.6) where MIDI support has
been separated out from the individual card drivers. try modprobing
snd-mpu401 with appropriate parameters. If this turns out to be a bug in the
kernel implementation, it would be useful to report this on the AGNULA user
list <users(a)lists.agnula.org>rg>.
cheers,
tim hall
http://glastonburymusic.org.uk
11:47 a.m.
tim hall wrote:
There is now a 2.6.12-3-multimedia-* kernel available
from Agnula,
the problems you describe may have been fixed (I don't know).
It's likely to be a configuration problem, there haven't been any
changes in the kernel that should affect the MidiSport 2x2.
This may also be due to changes in the ALSA modules
(since >=
1.0.6) where MIDI support has been separated out from the
individual card drivers. try modprobing snd-mpu401 with
appropriate parameters.
The MidiSport uses an embedded i8051-compatible processor, not an
Intel southbridge. :-) Changes in the snd-intel8x0/snd-mpu401 drivers
don't affect USB devices.
HTH
Clemens
4:16 p.m.
Last Monday 04 July 2005 14:47, Clemens Ladisch was like:
tim hall wrote:
OK, thanks for the clarification, Clemens.
cheers,
tim hall
http://glastonburymusic.org.uk
There is now a 2.6.12-3-multimedia-* kernel
available from Agnula,
the problems you describe may have been fixed (I don't know).
It's likely to be a configuration problem, there haven't been any
changes in the kernel that should affect the MidiSport 2x2.
This may also be due to changes in the ALSA
modules (since >=
1.0.6) where MIDI support has been separated out from the
individual card drivers. try modprobing snd-mpu401 with
appropriate parameters.
The MidiSport uses an embedded i8051-compatible processor, not an
Intel southbridge. :-) Changes in the snd-intel8x0/snd-mpu401 drivers
don't affect USB devices. 
4:32 p.m.
I'm having problem too with my midisport 2x2.Wether with kernels 2.6.12-2
or 2.6.12-3, it is not powered by its usb port.Does yours powered on (green
light) ?
The trick i'm using right now is booting first Windows that powers it
correctly then rebooting to demudi.Then it's correctly powered.If i stop the
machine and start it straight to demudi, it's never powered.
Hope it works for you.but that's jiust a workaround (not very funny to boot
windows first...)
----- Original Message -----
From: "Stephen Ceresia" <chungkingmansions(a)gmail.com>
To: <linux-audio-user(a)music.columbia.edu>
Sent: Monday, July 04, 2005 7:44 AM
Subject: [linux-audio-user] midisport 2x2
Hi all,
I recently upgraded to kernel 2.6.12-2multimedia-386, and I seem to
have killed my perfectly functioning Midisport 2x2. When I launch
seq24, the Midisport outputs no longer appears as options. It seems
that my cheap onboard laptop soundcard has been defaulted to take care
of MIDI. The firmware appears to load successfully, and I've tried
doing $ modprobe snd-seq , but no luck. Any suggestions would be
greatly appreciated... I just got some new gear and was having a great
time sequencing... what bad timing!
Stephen
6:29 p.m.
svoufff wrote:
I'm having problem too with my midisport 2x2.Wether
with kernels 2.6.12-2
or 2.6.12-3, it is not powered by its usb port.Does yours powered on (green
light) ?
The trick i'm using right now is booting first Windows that powers it
correctly then rebooting to demudi.Then it's correctly powered.If i stop the
machine and start it straight to demudi, it's never powered.
Hope it works for you.but that's jiust a workaround (not very funny to boot
windows first...)
----- Original Message -----
From: "Stephen Ceresia" <chungkingmansions(a)gmail.com>
To: <linux-audio-user(a)music.columbia.edu>
Sent: Monday, July 04, 2005 7:44 AM
Subject: [linux-audio-user] midisport 2x2
>Hi all,
>
>I recently upgraded to kernel 2.6.12-2multimedia-386, and I seem to
>have killed my perfectly functioning Midisport 2x2. When I launch
>seq24, the Midisport outputs no longer appears as options. It seems
>that my cheap onboard laptop soundcard has been defaulted to take care
>of MIDI. The firmware appears to load successfully, and I've tried
>doing $ modprobe snd-seq , but no luck. Any suggestions would be
>greatly appreciated... I just got some new gear and was having a great
>time sequencing... what bad timing!
>
>Stephen
>
>
Firmware has to be loaded into the Midisport 2x2 for it to operate. In
Windows this is done by whatever software was installed for this device,
and in Linux hotplug calls fxload to do the same.
The whole story and firmware are available under
ezusbmidi_2002_11_17.noarch.rpm or whatever other format you need.
With Fedora Core 3 running on 2.6.11-1.27FC3smp the 2x2 fires right up
when plugged in or if already plugged, at bootup. Fxload is already
present in /sbin, two files (loader instructions and devices map) go in
/etc/hotplug/usb, and two firmware files go in /usr/share/usb/ezusbmidi
- it's just that simple.
Frank
10:22 p.m.
I've done that already, it works if i unplug then replug the interface, but
it's still not powered up after a machine start.Nothing in dmesg either.All
the files are there but nothing happens.
On the usb port next to this one , i have a Iriver player connected and it
works perfect, but no way to fire up the 2x2.
Thanks anyway for the help.
Firmware has to be loaded into the Midisport 2x2 for
it to operate. In
Windows this is done by whatever software was installed for this device,
and in Linux hotplug calls fxload to do the same.
The whole story and firmware are available under
ezusbmidi_2002_11_17.noarch.rpm or whatever other format you need.
With Fedora Core 3 running on 2.6.11-1.27FC3smp the 2x2 fires right up
when plugged in or if already plugged, at bootup. Fxload is already
present in /sbin, two files (loader instructions and devices map) go in
/etc/hotplug/usb, and two firmware files go in /usr/share/usb/ezusbmidi
- it's just that simple.
Frank
5 Jul
5 Jul
12:55 a.m.
svoufff wrote:
I've done that already, it works if i unplug then
replug the interface, but
it's still not powered up after a machine start.Nothing in dmesg either.All
the files are there but nothing happens.
On the usb port next to this one , i have a Iriver player connected and it
works perfect, but no way to fire up the 2x2.
Thanks anyway for the help.
You're welcome, but permit me one last try: If replugging starts
everything up successfully, something is wrong with hotplug's
configuration, at least as regards it's behavior upon bootup.
If there are no relevant messages in dmesg and messages, you'll be
flying a little blind here, but I'd take a look at the loaded modules
(lsmod and lsmod | grep snd) after a boot and again after a replug of
the 2x2. If you see anything different, (and I'd also again take a peek
at the log files to see what this replug accomplished) that might give
you a clue.
What I'm thinking is the /etc/hotplug/blacklist file where you can place
modules that might conflict with the Midisport's starting. I had audio
and usbmidi in my old blacklist from RedHat 8.0 where the OSS drivers
were inclined to conflict with the ALSA ones. Without these, bootup was
erratic. Sometimes the 2x2 would light up and other times not.
You probably don't have this problem with your newer distro, but I am
not familiar with Debian. Still, this is all I know first-hand. Anyone
else?
Frank
3:26 p.m.
I finally found out : was an obsure problem of syntax in the file
/etc/hotplug/usb/midisport_fw
Found that on the usb-midi-fw-user mailing list.
The thread is here
http://sourceforge.net/mailarchive/forum.php?thread_id=6911828&forum_id…
7
Thanks mucho to all for the time given.
----- Original Message -----
From: "pirrone" <pirrone(a)localnet.com>
To: "A list for linux audio users" <linux-audio-user(a)music.columbia.edu>
Sent: Tuesday, July 05, 2005 6:54 AM
Subject: Re: [linux-audio-user] midisport 2x2
You're welcome, but permit me one last try: If
replugging starts
everything up successfully, something is wrong with hotplug's
configuration, at least as regards it's behavior upon bootup.
If there are no relevant messages in dmesg and messages, you'll be
flying a little blind here, but I'd take a look at the loaded modules
(lsmod and lsmod | grep snd) after a boot and again after a replug of
the 2x2. If you see anything different, (and I'd also again take a peek
at the log files to see what this replug accomplished) that might give
you a clue.
What I'm thinking is the /etc/hotplug/blacklist file where you can place
modules that might conflict with the Midisport's starting. I had audio
and usbmidi in my old blacklist from RedHat 8.0 where the OSS drivers
were inclined to conflict with the ALSA ones. Without these, bootup was
erratic. Sometimes the 2x2 would light up and other times not.
You probably don't have this problem with your newer distro, but I am
not familiar with Debian. Still, this is all I know first-hand. Anyone
else?
Frank
3:45 p.m.
Sorry, bad link, the right adress of the thread is
http://sourceforge.net/mailarchive/forum.php?thread_id=6911828&forum_id…
7
----- Original Message -----
From: "svoufff" <svoufff(a)free.fr>
To: "A list for linux audio users" <linux-audio-user(a)music.columbia.edu>
Sent: Tuesday, July 05, 2005 9:25 PM
Subject: Re: [linux-audio-user] midisport 2x2
I finally found out : was an obsure problem of syntax
in the file
/etc/hotplug/usb/midisport_fw
Found that on the usb-midi-fw-user mailing list.
The thread is here
http://sourceforge.net/mailarchive/forum.php?thread_id=6911828&forum_id…
7
Thanks mucho to all for the time given.
7083
days inactive
7085
days old
linux-audio-user@lists.linuxaudio.org
12 comments
6 participants
participants (6)
-
Clemens Ladisch -
Kevin Cosgrove -
pirrone -
Stephen Ceresia -
svoufff -
tim hall