Newbie having trouble with Broadcom 4311 wireless and M-Audio Ozone

  • thunder
Posted: Wed, 08/15/2007 - 02:18
Hello, Im pretty new to using Linux and have been using MEPIS distro for about 3 weeks, otherwise I've been trapped in a Windows box for what could be seen as an eternity. Well I am looking for alternitive to Windows and of course my audio tools. I currently use Reason 3.0 (Love it) and Adobe Audition for my projects and I like it as well, but both require either Windows or Mac. I want something more, something dedicated to music, but I need to be able to connect to the internet for updates and project sharing and I need to be able to use my Ozone and it looks like 64Studio is what I am looking for. Can anyone please help me with the configuration of both of these devices? My computer is a: Compaq Presario V6205nr, Turion 64, 1gb of RAM Wireless is Broadcom 4311 Video is NVIDIA GeForce 6150 Audio Hardware is M-Audio Ozone and generic sound device built into laptop. Thank you very much for your help.

M-Audio Ozone

  • kaimerra
  • 11/14/08
  • Sun, 01/04/2009 - 09:36
Hey there, I have my Ozone working on my Ubuntu Studio Hardy box as well as my 64 Studio 2.1 box. I followed the instructions at the thread below to get it working. Assuming that you see your Ozone when you type "lsusb" into a console, it should show up as something like "Midiman". I didn't have to do steps 1-10, I think it may have to do with making it your default sound device. But when you start Jack audio server you can just tell it to use your internal card or the Ozone, so I don't think you need to worry about it. But when you get to step 22, and you add that line to your /etc/udev/rules.d/42-madfuload.rules file. I had to change the "SUBSYSTEM=="usb_device" to "SUBSYSTEM=="usb". you may have to as well. Once you finish the udev install and get it configured and all, it should work like a charm. Mine works as an audio interface and MIDI controller great. I use my Ozone with a ol' T22 Thinkpad running 64 Studio as my live performance synth/sampler instrument. Best of luck on your Linux adventures, once you get it workin its rock solid.

M-audio Ozone

  • cinder
  • 10/20/08
  • Mon, 01/05/2009 - 11:21
Thanks a million kaimerra! I just installed the firmware loader (v1.2) and it works. Thats it, it just works. I didn't edit any udev rules, I haven't got an .asoundrc file yet or anything. This is so great! 64studio rules! It kiks ass! It's Rock 'n' Roll! (... yeah! ALSA too) ...(yeah! and jack too) Timing is Everything! P.S. Download the firmware loaders for several M-audio/Midiman products here:

Broadcom wireless

  • Daniel
  • 05/22/07
  • Wed, 08/15/2007 - 14:17
The Broadcom 4311 should work with 64 Studio 2.0, but these chipsets can be tricky to set up. You can either use the native bcm43xx driver, or the Windows driver with ndiswrapper.

Thanks for your reply. I

  • thunder
  • 08/14/07
  • Sun, 08/19/2007 - 21:02
Thanks for your reply. I have very little experience using Linux. I have run the Live CD and it doesn't recognize my wireless, so if you could help me or give me some clues on how to install the drivers and make them work, it would be much appreciated. I really want to make this work. Im sick of Windows and its over bloated OS. Thanks again for your help. Regards Tim

Class complient?

  • Quentin Harley
  • 05/24/07
  • Wed, 08/15/2007 - 06:41
I vaguely remember reading that the Ozone is supposed to be class compliant, and should work out of box. Doing a quick search I discovered that there might be some firmware to be loaded to the unit. I have very limited experience with usb audio devices, my only one being a midi interface (class compliant and it just works!) I suggest you download the 64studio live CD and try it on your system (you don't have to install) - just boot off the CD You won't loose anything on your hard drives, but the usage is a little limited. Just to give you an idea of how it might run on your system. Hope it helps,

Hi, thanks for your help.

  • thunder
  • 08/14/07
  • Sun, 08/19/2007 - 21:11
Hi, thanks for your help. Could you be more specific with the firmware updates and what I ahve to do to make it work in 64Studio/ I have the live CD and thinks that 64 studio is great because the OS is strriped down and ready to rock. I love the flexability of Linux and really want this to be it. My Ozone is also a Midi Controller and digital audio interface and I got it to work once using Mepis, but only once and I don't know what I did. Can you see my delima, if this was Windows or DOS Id have it working because I am very familiar with them and their quirky behavior, but I know nothing about Linux. Its like learning a whole new way of computing. Anyway, I appriciate your help any more elaboration would be greatly appreciated... Thank you Tim

M-audio Ozone

  • cinder
  • 10/20/08
  • Sat, 01/03/2009 - 09:55
Hello tim! I've been racking my racking my brain reasearching and trying to get an M-Audio Ozone to work as well. I was intrigued whe I read that you had got it work once on Mepis. I've read elswhere that there could be minor variations and revisions with the same model names. Mine has no indications that I can see, other than a serial number, whitch hasn't yielded any results on google. However, I have come across some potential leads reading A LOT of documentation(I'm new to linux) about devices and udev and this seemingly obscure little bit of old ALSA driver code called usbquirk.h;diffvar=v In this code there are some lines refering to the Ozone. All usb devices have Product and Vender ID's. The Product ID referenced in afore mention code is slightly different from what I get when I look at my system file /proc/bus/usb/devices or run lsusb in a terminal. ... if I type: cat /proc/bus/usb/devices ...I get: T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=fe(app. ) Sub=01 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0763 ProdID=2808 Rev= 1.00 S: Manufacturer=Unknown S: Product=Unknown C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none) ...the Vendor ID in in the usbquirk.h(theres actualy two versions, and 2.6.25) the one I have are the same (0763), but the product ID reads 2008, while I have 2808. If you say the unit has worked in the past and this usbquirk.h header code is pretty old, then maybe by matching the Product IDs and compiling or patching the ALSA driver, it'll work. I mean it is bieng recignized, I've comunicated with it, and it works wingdoze. I would like to know what your Product ID is. I'm running 64studio 2.1 i386 with a Timing is Everything!