17 Jun
2007
17 Jun
'07
12:31 a.m.
I am getting a 64-bit system later this week and will be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW, and
I will be mocing my Delta1010 audio interface over to this new machine
also. Are there any general 'gotchas' with regard to Linux audio and
64-bit hardware?
-- Brett
------------------------------------------------------------
"In the rhythm of music a secret is hidden;
If I were to divulge it, it would overturn the world."
-- Jelaleddin Rumi
17 Jun
17 Jun
12:41 a.m.
On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W. McCoy wrote:
I am getting a 64-bit system later this week and will
be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW, and
I will be mocing my Delta1010 audio interface over to this new machine
also. Are there any general 'gotchas' with regard to Linux audio and
64-bit hardware?
not with the hardware. with the software, the VM based scientific audio stuff tends to be
broken - at least SCLang, PD, and Chuck. not sure about CSound. so if youre into that
stuff, youll need a 32bit chroot. or you could control scserver from haskell or scheme...
all the normal stuff works fine, and has for a couple years now..
-- Brett
------------------------------------------------------------
"In the rhythm of music a secret is hidden;
If I were to divulge it, it would overturn the world."
-- Jelaleddin Rumi
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
12:46 a.m.
On 6/16/07, carmen <_(a)whats-your.name> wrote:
On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W.
McCoy wrote:
Just using the standard studio stuff: Jack, Ardour, Jamin, Rosegarden,
Hydrogen, etc.
-- Brett
------------------------------------------------------------
"In the rhythm of music a secret is hidden;
If I were to divulge it, it would overturn the world."
-- Jelaleddin Rumi
I am getting a 64-bit system later this week and
will be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW, and
I will be mocing my Delta1010 audio interface over to this new machine
also. Are there any general 'gotchas' with regard to Linux audio and
64-bit hardware?
not with the hardware. with the software, the VM based scientific audio stuff tends to be
broken - at least SCLang, PD, and Chuck. not sure about CSound. so if youre into that
stuff, youll need a 32bit chroot. or you could control scserver from haskell or scheme...
3:03 a.m.
On 16 June 2007 at 22:46, "Brett W. McCoy" <idragosani(a)gmail.com> wrote:
Just using the standard studio stuff: Jack, Ardour,
Jamin, Rosegarden,
Hydrogen, etc.
I'm in the same situation as you. I have an Athlon 64-X2 machine
on which I run a 32-bit SMP multimedia kernel. I haven't thought to
try the 64-bit stuff fully yet. Please do let us know how it works
for you, what works, what doesn't. Thanks!
--
Kevin
1:12 a.m.
carmen wrote:
not with the hardware. with the software, the VM based
scientific
audio stuff tends to be broken - at least SCLang, PD, and Chuck.
not sure about CSound.
Csound is fine on 64 bit.
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"Well behaved women rarely make history." -- Dorothy Parker
8:30 a.m.
On Sat, 2007-06-16 at 22:41 -0400, carmen wrote:
On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W.
McCoy wrote:
is it possible to connect to a 64-bit jack from within a 32-bit chroot?
thnx, tim
--
tim(a)klingt.org ICQ: 96771783
http://tim.klingt.org
Relying on the government to protect your privacy is like asking a
peeping tom to install your window blinds.
John Perry Barlow
I am getting a 64-bit system later this week and
will be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW,
and
I will be mocing my Delta1010 audio interface
over to this new
machine
also. Are there any general 'gotchas'
with regard to Linux audio
and
64-bit hardware?
not with the hardware. with the software, the VM based scientific
audio stuff tends to be broken - at least SCLang, PD, and Chuck. not
sure about CSound. so if youre into that stuff, youll need a 32bit
chroot. or you could control scserver from haskell or scheme... 
9:56 a.m.
Tim Blechmann wrote:
On Sat, 2007-06-16 at 22:41 -0400, carmen wrote:
good question, i dont think it will work but i never tried, if i try it
soon enough ill reply it here.
On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W.
McCoy wrote:
is it possible to connect to a 64-bit jack from within a 32-bit chroot?
thnx, tim
--
tim(a)klingt.org ICQ: 96771783
http://tim.klingt.org
Relying on the government to protect your privacy is like asking a
peeping tom to install your window blinds.
John Perry Barlow
------------------------------------------------------------------------
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
I am getting a 64-bit system later this week and
will be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW,
and
I will be mocing my Delta1010 audio interface
over to this new
machine
also. Are there any general 'gotchas'
with regard to Linux audio
and
64-bit hardware?
not with the hardware. with the software, the VM based scientific
audio stuff tends to be broken - at least SCLang, PD, and Chuck. not
sure about CSound. so if youre into that stuff, youll need a 32bit
chroot. or you could control scserver from haskell or scheme...
10:12 a.m.
On 6/17/07, Tim Blechmann <tim(a)klingt.org> wrote:
On Sat, 2007-06-16 at 22:41 -0400, carmen wrote:
No.
Maybe someday, but it's hard and has not been high-priority.
--
joq
On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W.
McCoy wrote:
is it possible to connect to a 64-bit jack from within a 32-bit chroot? I am getting a 64-bit system later this week and
will be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW,
and
I will be mocing my Delta1010 audio interface
over to this new
machine
also. Are there any general 'gotchas'
with regard to Linux audio
and
64-bit hardware?
not with the hardware. with the software, the VM based scientific
audio stuff tends to be broken - at least SCLang, PD, and Chuck. not
sure about CSound. so if youre into that stuff, youll need a 32bit
chroot. or you could control scserver from haskell or scheme... 
2:40 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Jun 17, 2007 at 07:12:54AM -0500, Jack O'Quin wrote:
On 6/17/07, Tim Blechmann <tim(a)klingt.org>
wrote:
Something that is on my TO-DO list but is likely never to get done, is to create a bi-arch
Debian package of jackd and a couple of its dependencies. Then, one may build and run
ChucK or SClang using 32-bit libjack, without a chroot.
This is how many non-64-bit-safe programs run today.
$ find /usr/lib32/ -type f | wc -l
714
So, on my Intel Core 2 Duo Debian Sid system, roughly 714 libraries have 32-bit alternate
versions, for use by apps that are not 64-bit safe. This is a tiny percentage compared to
the 64-bit libraries, by the way:
$ find /usr/lib64/ -type f | wc -l
13443
But, I'd propose that a simultaneous installation of 64-bit and 32-bit versions of
libjack, each in their appropriate location in /usr/lib32 and /usr/lib64, would be cleaner
and more transparent for the user than creating chroots and such.
- -ken
On Sat, 2007-06-16 at 22:41 -0400, carmen wrote:
No.
Maybe someday, but it's hard and has not been high-priority. On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W.
McCoy wrote:
is it possible to connect to a 64-bit jack from within a 32-bit chroot? I am getting a 64-bit system later this week and
will be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW,
and
I will be mocing my Delta1010 audio interface
over to this new
machine
also. Are there any general 'gotchas'
with regard to Linux audio
and
64-bit hardware?
not with the hardware. with the software, the VM based scientific
audio stuff tends to be broken - at least SCLang, PD, and Chuck. not
sure about CSound. so if youre into that stuff, youll need a 32bit
chroot. or you could control scserver from haskell or scheme... -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGdWPme8HF+6xeOIcRAq0fAKDG99ruJUO3ly9mOTSohfTTuh/lnACdE0+G
Z6T1sumB0ckODcOz01D5zmo=
=ldpp
-----END PGP SIGNATURE-----
18 Jun
18 Jun
1:35 a.m.
On 6/17/07, Ken Restivo <ken(a)restivo.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Jun 17, 2007 at 07:12:54AM -0500, Jack O'Quin wrote:
There is no point in doing all that until we release a version
of jackd that can handle both 32-bit and 64-bit clients accessing
the same shared memory segments. Right now that is not
possible. There are some pointers, for example, in shared
memory. That will not work and must be changed. The jackd
modifications required are doable (IMHO), but definitely not
easy.
To date, there have been no large number of requests on
jackit-devel or on LAU for this feature. So, people tend
to classify it as a post-1.0 work item.
--
joq
On 6/17/07, Tim Blechmann <tim(a)klingt.org>
wrote:
Something that is on my TO-DO list but is likely never to get done, is to create a
bi-arch Debian package of jackd and a couple of its dependencies. Then, one may build and
run ChucK or SClang using 32-bit libjack, without a chroot.
This is how many non-64-bit-safe programs run today.
$ find /usr/lib32/ -type f | wc -l
714
So, on my Intel Core 2 Duo Debian Sid system, roughly 714 libraries have 32-bit alternate
versions, for use by apps that are not 64-bit safe. This is a tiny percentage compared to
the 64-bit libraries, by the way:
$ find /usr/lib64/ -type f | wc -l
13443
But, I'd propose that a simultaneous installation of 64-bit and 32-bit versions of
libjack, each in their appropriate location in /usr/lib32 and /usr/lib64, would be cleaner
and more transparent for the user than creating chroots and such. On Sat, 2007-06-16 at 22:41 -0400, carmen wrote:
No.
Maybe someday, but it's hard and has not been high-priority. On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W.
McCoy wrote:
> I am getting a 64-bit system later this week and will be installing
> Fedora Core 6 x64 and it will be replacing my current studio DAW,
and
> I will be mocing my Delta1010 audio interface over to this new
machine
> also. Are there any general 'gotchas' with regard to Linux audio
and
> 64-bit hardware?
not with the hardware. with the software, the VM based scientific
audio stuff tends to be broken - at least SCLang, PD, and Chuck. not
sure about CSound. so if youre into that stuff, youll need a 32bit
chroot. or you could control scserver from haskell or scheme...
is it possible to connect to a 64-bit jack from within a 32-bit chroot?
3:25 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Jun 17, 2007 at 10:35:51PM -0500, Jack O'Quin wrote:
On 6/17/07, Ken Restivo <ken(a)restivo.org>
wrote:
Thanks.
Hmm. If there are issues with pointer size, I'd expect that a 32-bit chroot
wouldn't work either.
The correct solution would be to fix the languages to make them 64-bit safe, but as you
know that is a non-trivial exercise.
I will make a note in to try these languages again sometime in 2009, and see if by then
they either are 64-bit safe or JACK would be able to accomodate them with concurrent use
of 32-bit/64-bit libraries at that time.
Thanks again!
- -ken
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Jun 17, 2007 at 07:12:54AM -0500, Jack O'Quin wrote:
There is no point in doing all that until we release a version
of jackd that can handle both 32-bit and 64-bit clients accessing
the same shared memory segments. Right now that is not
possible. There are some pointers, for example, in shared
memory. That will not work and must be changed. The jackd
modifications required are doable (IMHO), but definitely not
easy.
To date, there have been no large number of requests on
jackit-devel or on LAU for this feature. So, people tend
to classify it as a post-1.0 work item. On 6/17/07, Tim Blechmann <tim(a)klingt.org>
wrote:
Something that is on my TO-DO list but is likely never to get done, is to
create a bi-arch Debian package of jackd and a couple of its dependencies.
Then, one may build and run ChucK or SClang using 32-bit libjack, without
a chroot.
This is how many non-64-bit-safe programs run today.
$ find /usr/lib32/ -type f | wc -l
714
So, on my Intel Core 2 Duo Debian Sid system, roughly 714 libraries have
32-bit alternate versions, for use by apps that are not 64-bit safe. This
is a tiny percentage compared to the 64-bit libraries, by the way:
$ find /usr/lib64/ -type f | wc -l
13443
But, I'd propose that a simultaneous installation of 64-bit and 32-bit
versions of libjack, each in their appropriate location in /usr/lib32 and
/usr/lib64, would be cleaner and more transparent for the user than
creating chroots and such. On Sat, 2007-06-16 at 22:41 -0400, carmen wrote:
> On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W. McCoy wrote:
> > I am getting a 64-bit system later this week and will be installing
> > Fedora Core 6 x64 and it will be replacing my current studio DAW,
> and
> > I will be mocing my Delta1010 audio interface over to this new
> machine
> > also. Are there any general 'gotchas' with regard to Linux audio
> and
> > 64-bit hardware?
>
> not with the hardware. with the software, the VM based scientific
> audio stuff tends to be broken - at least SCLang, PD, and Chuck. not
> sure about CSound. so if youre into that stuff, youll need a 32bit
> chroot. or you could control scserver from haskell or scheme...
is it possible to connect to a 64-bit jack from within a 32-bit chroot?
No.
Maybe someday, but it's hard and has not been high-priority. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGdhcve8HF+6xeOIcRAjjuAJ98gj7xo+hBZnXxy4pB9t6C4YJiSgCggyQP
AftRKJWGqXCNT/A8ACImbiw=
=tsXS
-----END PGP SIGNATURE-----
4:02 a.m.
On 6/16/07, carmen <_(a)whats-your.name> wrote:
On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W. McCoy wrote:
Alas, me, I can't get my ethernet, wireless, or audio to work with any
linux. Got the machine in November, and supposedly those issues have been
worked out, but I can't get around them.
So I guess a gotcha is if you don't check all the hardware for drivers
first.
-Chuckk
I am getting a 64-bit system later this week and
will be installing
Fedora Core 6 x64 and it will be replacing my current studio DAW, and
I will be mocing my Delta1010 audio interface over to this new machine
also. Are there any general 'gotchas' with regard to Linux audio and
64-bit hardware?
not with the hardware. 
4:34 a.m.
Chuckk Hubbard wrote:
On 6/16/07, *carmen* <_(a)whats-your.name
<http://whats-your.name>> wrote:
On Sat Jun 16, 2007 at 10:30:48PM -0400, Brett W. McCoy wrote:
My understanding is that there are still fewer 64-bit device drivers
than 32-bit ones. I don't know. Only computer I've encountered that
wouldn't run Linux was an old Dell; it would try to boot but nothing I
tried would get it past freezing. But I'm a bottom feeder, 64-bit
machines aren't in my price range.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
I am getting a 64-bit system later this week and
will be installing
Fedora Core 6 x64 and it will be replacing my current studio
DAW, and
I will be mocing my Delta1010 audio interface
over to this new
machine
also. Are there any general 'gotchas'
with regard to Linux audio and
64-bit hardware?
not with the hardware.
Alas, me, I can't get my ethernet, wireless, or audio to work with any
linux. Got the machine in November, and supposedly those issues have
been worked out, but I can't get around them.
So I guess a gotcha is if you don't check all the hardware for drivers
first.
23 Jun
23 Jun
1:17 p.m.
On 6/18/07, david <gnome(a)hawaii.rr.com> wrote:
Chuckk Hubbard wrote:
Alas, me, I can't get my ethernet, wireless, or
audio to work with any
I hear that. Apparently the only 64-bit machines in my price range take the
lowest bidder for wireless and audio chips.
-Chuckk
linux. Got the machine in November, and
supposedly those issues have
been worked out, but I can't get around them.
So I guess a gotcha is if you don't check all the hardware for drivers
first.
My understanding is that there are still fewer 64-bit device drivers
than 32-bit ones. I don't know. Only computer I've encountered that
wouldn't run Linux was an old Dell; it would try to boot but nothing I
tried would get it past freezing. But I'm a bottom feeder, 64-bit
machines aren't in my price range.
6:35 p.m.
Chuckk Hubbard wrote:
On 6/18/07, *david* <gnome(a)hawaii.rr.com
<mailto:gnome@hawaii.rr.com>>
wrote:
Chuckk Hubbard wrote:
Hmm, the Atheros wireless chipsets seem to have good support in general
- I'd think one of theirs would work. Don't know about audio chips - my
cheapie is an Intel and it works good enough for my composition work.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Alas, me, I can't get my ethernet, wireless,
or audio to work
with any
linux. Got the machine in November, and
supposedly those issues have
been worked out, but I can't get around them.
So I guess a gotcha is if you don't check all the hardware for
drivers
first.
My understanding is that there are still fewer 64-bit device drivers
than 32-bit ones. I don't know. Only computer I've encountered that
wouldn't run Linux was an old Dell; it would try to boot but nothing I
tried would get it past freezing. But I'm a bottom feeder, 64-bit
machines aren't in my price range.
I hear that. Apparently the only 64-bit machines in my price range take
the lowest bidder for wireless and audio chips. 
24 Jun
24 Jun
7:08 a.m.
Am Samstag, den 23.06.2007, 10:35 -1000 schrieb david:
Hmm, the Atheros wireless chipsets seem to have good support in
general
I have an abit airpace (desktop wlan card) with an atheros chipset.
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG
802.11 b/g Wireless PCI Express Adapter (rev 01)
I could not get this to work.
the hal refuses to load on this chipset, cause the subsystem IDs (!!)
are not known to it. openhal doesn't support it, so also no luck.
the last resort was ndiswrapper, so i tried to d/l some generic xp64
drivers for this chipset, but you guessed - it also doesn't work.
and i can't use the original drivers from abit, cause they were smart
enough to stick all files in an installshield sfx. unshield doesn't
work, and under wine explains me that it it found no drivers.
having that said - i could easily find an intel 3945abg for € 30,- on
ebay. but this doesn't help me on my desktop ...
- I'd think one of theirs would work. Don't
know about audio chips -
my
cheapie is an Intel and it works good enough for my composition work.
26 Jun
26 Jun
2:28 a.m.
Thomas Ilnseher wrote:
Am Samstag, den 23.06.2007, 10:35 -1000 schrieb
david:
Hmmm, I never went through HAL for wireless support. I downloaded and
compiled the WiFi drivers. But I don't have that chipset or 64-bit
hardware - the 64-bit hardware might be the source of the problem.
Hmm, the Atheros wireless chipsets seem to have
good support in
general
I have an abit airpace (desktop wlan card) with an atheros chipset.
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG
802.11 b/g Wireless PCI Express Adapter (rev 01)
I could not get this to work.
the hal refuses to load on this chipset, cause the subsystem IDs (!!)
are not known to it. openhal doesn't support it, so also no luck. the last resort was ndiswrapper, so i tried to d/l
some generic xp64
drivers for this chipset, but you guessed - it also doesn't work.
Probably a victim of trying to run 32-bit software (ndiswrapper) under
64-bit Linux. Or is there a 64-bit version of ndiswrapper?
and i can't use the original drivers from abit,
cause they were smart
enough to stick all files in an installshield sfx. unshield doesn't
work,
Perhaps orange would?
and under wine explains me that it it found no
drivers.
WINE is 32-bit, perhaps it's looking for 32-bit drivers, not 64-bit.
Sounds like 64-bit doesn't quite have as much driver support as it should.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
5:51 a.m.
Am Montag, den 25.06.2007, 18:28 -1000 schrieb david:
there is a 64bit version of ndiswrapper. (of course you need XP 64 bit
windowze drivers).
obviously, I would not have been able to compile, and load 32bit stuff
in an 64 bit kernel.
nice info, thx a lot. I'll try it.
nope. the
problem is that wine doesn't wrap / emulate the windows calls
to inquiry the hardware.
Thomas Ilnseher wrote:
No the hal in
this case is NOT the hald you might refer to. It's the
module ath_hal.ko that comes with madwifi. This consists of a closed
source lib and some interface glue c files. this module creates an
abstract if to the hardware, which the madwifi driver itself uses.
Am Samstag, den 23.06.2007, 10:35 -1000 schrieb
david:
Hmmm, I never went through HAL for wireless support. I downloaded and
compiled the WiFi drivers. But I don't have that chipset or 64-bit
hardware - the 64-bit hardware might be the source of the problem. Hmm, the Atheros wireless chipsets seem to have
good support in
general
I have an abit airpace (desktop wlan card) with an atheros chipset.
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG
802.11 b/g Wireless PCI Express Adapter (rev 01)
I could not get this to work.
the hal refuses to load on this chipset, cause the subsystem IDs (!!)
are not known to it. openhal doesn't support it, so also no luck. the last resort was ndiswrapper, so i tried to
d/l some generic xp64
drivers for this chipset, but you guessed - it also doesn't work.
Probably a victim of trying to run 32-bit software (ndiswrapper) under
64-bit Linux. Or is there a 64-bit version of ndiswrapper?
and i
can't use the original drivers from abit, cause they were smart
enough to stick all files in an installshield sfx. unshield doesn't
work,
Perhaps orange would? and under wine explains me that it it found no
drivers.
WINE is 32-bit, perhaps it's looking for 32-bit drivers, not 64-bit.
Sounds like 64-bit doesn't quite have as much driver support as it should.
This might be the case, but it's not the problem here. i tried to boot
of an livecd, and compiled madwifi for 32bit, and it still won't work.
This is an genuine problem with closed source drivers (tm).
6:39 a.m.
Thomas Ilnseher wrote:
there is a 64bit version of ndiswrapper. (of course you need XP 64 bit
windowze drivers).
obviously, I would not have been able to compile, and load 32bit stuff
in an 64 bit kernel.
Like I said, I'm a bottom feeder - my "fast hot machine" around here is
only a Sempron 1800+! ;-)
nice info, thx a lot. I'll try it.
Perhaps it will work. I don't know if it's using the same CAB libs that
unshield is using ...
nope. the problem is that wine doesn't wrap / emulate the windows calls
to inquiry the hardware.
Sounds like something to mention to WINE developers. They should at
least return information about whatever video/audio/network etc hardware
they DO emulate - WINE on my laptop here happily connects to the
internet when needed.
Ain't that the truth. You might try one of those USB external wireless
adapters, perhaps they'd work?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Am Montag, den 25.06.2007, 18:28 -1000 schrieb david:
OK, I didn't know that.
Thomas Ilnseher wrote:
No the hal in
this case is NOT the hald you might refer to. It's the
module ath_hal.ko that comes with madwifi. This consists of a closed
source lib and some interface glue c files. this module creates an
abstract if to the hardware, which the madwifi driver itself uses. Am Samstag, den 23.06.2007, 10:35 -1000 schrieb
david:
Hmmm, I
never went through HAL for wireless support. I downloaded and
compiled the WiFi drivers. But I don't have that chipset or 64-bit
hardware - the 64-bit hardware might be the source of the problem. Hmm, the Atheros wireless chipsets seem to have
good support in
general
I have an abit airpace (desktop wlan card) with an atheros chipset.
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG
802.11 b/g Wireless PCI Express Adapter (rev 01)
I could not get this to work.
the hal refuses to load on this chipset, cause the subsystem IDs (!!)
are not known to it. openhal doesn't support it, so also no luck. the last resort was ndiswrapper, so i tried to d/l
some generic xp64
drivers for this chipset, but you guessed - it also doesn't work.
Probably a
victim of trying to run 32-bit software (ndiswrapper) under
64-bit Linux. Or is there a 64-bit version of ndiswrapper?
and i can't use the original drivers from abit,
cause they were smart
enough to stick all files in an installshield sfx. unshield doesn't
work,
Perhaps orange would? and under wine explains me that it it found no
drivers.
WINE is 32-bit, perhaps it's looking for 32-bit drivers, not 64-bit.
Sounds like
64-bit doesn't quite have as much driver support as it should.
This might be the case, but it's not the problem here. i tried to boot
of an livecd, and compiled madwifi for 32bit, and it still won't work.
This is an genuine problem with closed source drivers (tm).
24 Jun
24 Jun
5:50 p.m.
On 6/23/07, david <gnome(a)hawaii.rr.com> wrote:
Chuckk Hubbard wrote:
I have the Broadcom curse.
nuff said.
--
http://www.badmuthahubbard.com
My understanding is that there are still
fewer 64-bit device drivers
than 32-bit ones. I don't know. Only computer I've encountered that
wouldn't run Linux was an old Dell; it would try to boot but nothing
I
tried would get it past freezing. But I'm
a bottom feeder, 64-bit
machines aren't in my price range.
I hear that. Apparently the only 64-bit machines in my price range take
the lowest bidder for wireless and audio chips.
Hmm, the Atheros wireless chipsets seem to have good support in general
- I'd think one of theirs would work. Don't know about audio chips - my
cheapie is an Intel and it works good enough for my composition work.
6152
days inactive
6162
days old
linux-audio-user@lists.linuxaudio.org
19 comments
11 participants
participants (11)
-
Brett W. McCoy -
carmen -
Chuckk Hubbard -
david -
Erik de Castro Lopo -
Glauber Prado -
Jack O'Quin -
Ken Restivo -
Kevin Cosgrove -
Thomas Ilnseher -
Tim Blechmann