Re: gcc4, thunderbird: emacs key bindings lost?
Javier Kohen wrote: > > I recall reading recently that having gtkspell installed caused the > Emacs key bindings to not work. Maybe this is the behavior you're > experiencing; I don't recall those key bindings working for me on TB on > pure64 (but I might be wrong, as I don't use TB anymore). > gtkspell is not (and was never, AFAIK) installed. But Firefox is affected by this, too, e.g. in the file browser. Regards Harri signature.asc Description: OpenPGP digital signature
Re: Octave
On Sun, 2005-05-08 at 23:33 +0200, Kurt Roeckx wrote: > On Sun, May 08, 2005 at 02:02:41PM -0700, Attila Kocsis wrote: > > Hi, > > Does anybody know if any 64-bit Octave version exist? > > Thx > > Yes, it's avaiable. The source package, and the real binary > pacakges are called octave2.1. > > However, I can't tell if the package works perfectly in 64 bit > mode or not, since I never used it. But I have no reason to > believe there is a problem with it. I believe that the current version, while working on 64bit architectures is really 32-bit in practice (i.e. it uses ints as indexes, therefore limiting data structures to 2GB). Clinton Chee at the UNSW HPC group has patches he's trying to get into the main tree. I'm not sure of the status of this, but I do know he has the test-suite passing on an SGI Altix. More information here: http://tinyurl.com/amsrh Cheers, Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SSH package concerns...
Nathan Dragun wrote: > While setting up PAM in conjunction with SSH I included the following > line to deny access unless found in the following file: > > authrequiredpam_listfile.so sense=allow onerr=fail item=user > file=/etc/sshloginusers > > Which works, sort of. Don't use it. sshd(8) lets you deny and allow users via /etc/ssh/sshd_config. Reading the daemon documentation before doing something like this is always good idea. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SSH package concerns...
This one time, at band camp, Nathan Dragun said: > While setting up PAM in conjunction with SSH I included the following > line to deny access unless found in the following file: > > authrequiredpam_listfile.so sense=allow onerr=fail item=user > file=/etc/sshloginusers > > Which works, sort of. > ...Lets say for examples sake the user "bob" is trying to get in, but is > not listed in this file. Ie: not authorized. If I try to connect via > the windows program PuTTY, the first attempt fails, naturally, but if I > re-type the password when prompted it will let me in!!! Not good. I > tested this several different ways and found that if I try and go from > linux box to linux box after about 4 attempts it will let me in. > > SSH package version: OpenSSH_3.8.1p1 Debian-8.sarge.4 > in conjunction with: OpenSSL 0.9.7e 25 Oct 2004 > > Now I was doing some research into this, figuring I configured something > wrong or what not early on when I first noticed this authentication > problem existed and noticed that there have been some huge changes from > the 3.8.1p1 release back in October 2004 (Ironically if I read that > right 4.0 was just released today). Changelog: > ftp://ftp.ca.openbsd.org/pub/OpenBSD/OpenSSH/portable/ChangeLog > > But, why on earth is this package so out of date?? Insight into this > would be greatly appreciated. What you are experiencing sounds like a configuration problem to me. You presumably have multiple auth mechanisms listed besides UsePam, and eventually one succeeds, although the PAM one failed. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - pgpRTwXLPWmrX.pgp Description: PGP signature
SSH package concerns...
While setting up PAM in conjunction with SSH I included the following line to deny access unless found in the following file: authrequiredpam_listfile.so sense=allow onerr=fail item=user file=/etc/sshloginusers Which works, sort of. ...Lets say for examples sake the user "bob" is trying to get in, but is not listed in this file. Ie: not authorized. If I try to connect via the windows program PuTTY, the first attempt fails, naturally, but if I re-type the password when prompted it will let me in!!! Not good. I tested this several different ways and found that if I try and go from linux box to linux box after about 4 attempts it will let me in. SSH package version: OpenSSH_3.8.1p1 Debian-8.sarge.4 in conjunction with: OpenSSL 0.9.7e 25 Oct 2004 Now I was doing some research into this, figuring I configured something wrong or what not early on when I first noticed this authentication problem existed and noticed that there have been some huge changes from the 3.8.1p1 release back in October 2004 (Ironically if I read that right 4.0 was just released today). Changelog: ftp://ftp.ca.openbsd.org/pub/OpenBSD/OpenSSH/portable/ChangeLog But, why on earth is this package so out of date?? Insight into this would be greatly appreciated. God Bless, Nathan Code is poetry. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt wants to remove bash, base-files; other move questions
On Tue, 2005-05-10 at 01:18 +0200, Goswin von Brederlow wrote: > I just told you where to look. Nothing against you. The ML archive is > full about this so everyone should be able to find it. The last big > thread was when the new libc6 got uploaded. Nothing against you either! I just wanted to try and explain that it's more difficult to deal with things that are only documented on a mailing list than people seem to realize. I wish there were a way I could help keep the project documentation more up to date. I could go update it with this information myself right now. I don't know how many pure64 users there are, but maybe even I won't be the last person to ask this? Regards, -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glx for ia32 applications does not work
El mar, 10-05-2005 a las 01:22 +0200, Alexander Fieroch escribiÃ: > Marcin DÄbicki wrote: > > A I remember Doom was the only game with this problem. I have juzt upgraded > > glibc and generated new cache for libs (also I didn't used chroot command > > itself to run Doom of course;)) > > No, I have the latest updates of debian sid and quake3 does not work > too. I don't have other games to test, but as I've said the glxgears in > ia32 chroot does not work too. So something does not work using ia32 > libs for glx. Does your user have permission to access DRI? Depending on the mode established in the DRI section of your XF86Config-4, you might need to add the user to a certain group. If it's 0666, then everybody can use DRI and you shouldn't worry about this. -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: glx for ia32 applications does not work
Marcin DÄbicki wrote: > A I remember Doom was the only game with this problem. I have juzt upgraded > glibc and generated new cache for libs (also I didn't used chroot command > itself to run Doom of course;)) No, I have the latest updates of debian sid and quake3 does not work too. I don't have other games to test, but as I've said the glxgears in ia32 chroot does not work too. So something does not work using ia32 libs for glx. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt wants to remove bash, base-files; other move questions
David Wood <[EMAIL PROTECTED]> writes: > OK, I'm guessing you guys tweaked the version numbering during the move? > So I think I need to force myself to a different version of base-files > and libc. We tweaked it about 4 month ago to get an unpached libc6 and base-files into sid amd64 and sarge amd64. Has nothing to do with the move. > Hey, I wonder what will happen if I'm wrong and I mess this up? hehe, sorry to do this to you, but thats also in the ML. You end up without ld where it should be and no dynamic binary starts anymore. Keep a boot cd ready if you are unsure. > Why don't I ask, just to be sure. > > And for this, I get the response above. > > You probably think I don't know what it's like to be in your shoes and > do a lot of work for nothing and have to answer stupid questions all the > time. You're wrong. I know what it's like. But do you know what it feels > like to try to use pure64 right now? > > Regards, > -David I just told you where to look. Nothing against you. The ML archive is full about this so everyone should be able to find it. The last big thread was when the new libc6 got uploaded. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt wants to remove bash, base-files; other move questions
On Mon, May 09, 2005 at 08:06:17PM -0300, Javier Kohen wrote: > David, the problem is that this question was answered five to ten > times in the last two weeks only; in fact, Goswin was the most > patient of all and always gave an answer in-line instead of sending > the poster to read the list. Definitely time for a FAQ or wiki update, then. ;-) You might cut these questions off before they're even asked. -- Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/ assert(expired(knowledge)); /* core dump */ signature.asc Description: Digital signature
Re: apt wants to remove bash, base-files; other move questions
El lun, 09-05-2005 a las 18:51 -0400, David Wood escribiÃ: > On Mon, 2005-05-09 at 23:21 +0200, Goswin von Brederlow wrote: > > And yet another person that hasn't been reading the ML for the last > > half year. Go fish. > > I know I'm ignorant and I screwed up, that much is obvious. But can I at > least tell you what this looked like from my perspective? David, the problem is that this question was answered five to ten times in the last two weeks only; in fact, Goswin was the most patient of all and always gave an answer in-line instead of sending the poster to read the list. They all had the same problem as you, and they all received a similar answer. It won't break if you follow the instructions in the previous threads. Or at least nobody complained so far if it broke for them. Greetings, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: apt wants to remove bash, base-files; other move questions
David Wood <[EMAIL PROTECTED]> writes: > Now using > > deb http://amd64.debian.net/debian/ sid main contrib > > An upgrade wants to remove base-files and bash. Digging deeper, I see > base-files is being removed because: > > base-files pre-depends on libc6 (< 2.3.2.dsl-20.0.1) > > I saw some traffic on the list that looked similar. But I don't > understand what you did, and I don't want to guess wrong and hose my > whole system. > > Do I want base-files 3.1.2-0.0.0.3.pure64? Or just 3.1.2? Update base-files to 3.1.2-0.0.1, or downgrade it to 3.1.2. Except for the version number, they are identical; 3.1.2 has just been rebuilt as 3.1.2-0.0.1 to have a newer version number than 3.1.2-0.0.0.3.pure64. > Do I want libc6 2.3.2.ds1-20.0.0.1.pure64? or 2.3.2.ds1-21? > > What is the safest way to handle this transition? After you have installed the appropriate base-files version, just perform an upgrade as usual. This should (possibly among other things) update libc6 to 2.3.2.ds1-21. Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt wants to remove bash, base-files; other move questions
On Mon, 2005-05-09 at 23:21 +0200, Goswin von Brederlow wrote:
> And yet another person that hasn't been reading the ML for the last
> half year. Go fish.
I know I'm ignorant and I screwed up, that much is obvious. But can I at
least tell you what this looked like from my perspective?
Is there any info on this move, this problem, anywhere other than this
mailing list?
I wasn't able to find it.
Your HOWTO isn't up to date. Your debian.org port page had some current
info but nothing about this problem.
Mailing lists are a disorganized, unreliable way to convey information.
I've been on the list for a while, but I'm not an expert like you and I
don't always understand everything or its relevance.
I also re-read the archives before I asked my question, and I said so
("I saw some traffic on the list that looked similar"). Searching on
libc gives a lot of hits that don't all immediately seem clear.
http://lists.debian.org/debian-amd64/2005/05/msg00151.html
This seems similar, but not quite the same problem. This looks closer:
http://lists.debian.org/debian-amd64/2005/04/msg00238.html
http://lists.debian.org/debian-amd64/2005/04/msg00242.html
OK, I'm guessing you guys tweaked the version numbering during the move?
So I think I need to force myself to a different version of base-files
and libc.
Hey, I wonder what will happen if I'm wrong and I mess this up?
Why don't I ask, just to be sure.
And for this, I get the response above.
You probably think I don't know what it's like to be in your shoes and
do a lot of work for nothing and have to answer stupid questions all the
time. You're wrong. I know what it's like. But do you know what it feels
like to try to use pure64 right now?
Regards,
-David
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt wants to remove bash, base-files; other move questions
David Wood <[EMAIL PROTECTED]> writes: > Now using > > deb http://amd64.debian.net/debian/ sid main contrib > > An upgrade wants to remove base-files and bash. Digging deeper, I see > base-files is being removed because: > > base-files pre-depends on libc6 (< 2.3.2.dsl-20.0.1) > > I saw some traffic on the list that looked similar. But I don't > understand what you did, and I don't want to guess wrong and hose my > whole system. > > Do I want base-files 3.1.2-0.0.0.3.pure64? Or just 3.1.2? > > Do I want libc6 2.3.2.ds1-20.0.0.1.pure64? or 2.3.2.ds1-21? > > What is the safest way to handle this transition? > > -David And yet another person that hasn't been reading the ML for the last half year. Go fish. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc4, thunderbird: emacs key bindings lost?
Hallo Harald, El lun, 09-05-2005 a las 23:02 +0200, Harald Dunkel escribiÃ: > Hi folks, > > Since the migration to gcc4 the Emacs key bindings in > Thunderbird's compose window seem to be gone. Is this > just me? I recall reading recently that having gtkspell installed caused the Emacs key bindings to not work. Maybe this is the behavior you're experiencing; I don't recall those key bindings working for me on TB on pure64 (but I might be wrong, as I don't use TB anymore). Greetings, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
gcc4, thunderbird: emacs key bindings lost?
Hi folks, Since the migration to gcc4 the Emacs key bindings in Thunderbird's compose window seem to be gone. Is this just me? Regards Harri signature.asc Description: OpenPGP digital signature
apt wants to remove bash, base-files; other move questions
Now using deb http://amd64.debian.net/debian/ sid main contrib An upgrade wants to remove base-files and bash. Digging deeper, I see base-files is being removed because: base-files pre-depends on libc6 (< 2.3.2.dsl-20.0.1) I saw some traffic on the list that looked similar. But I don't understand what you did, and I don't want to guess wrong and hose my whole system. Do I want base-files 3.1.2-0.0.0.3.pure64? Or just 3.1.2? Do I want libc6 2.3.2.ds1-20.0.0.1.pure64? or 2.3.2.ds1-21? What is the safest way to handle this transition? -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question
Lennart Sorensen kiedys napisal: > On Mon, May 09, 2005 at 08:12:44PM +0200, Marcin D?bicki wrote: >> I just wanted to say that the primary adapter I call this device is a >> device like Marvell Yukon (not Yukon) but nForce has an API used to hide >> real interface from OS. True adapter driver is on nvidia chipset because >> only chipset sees what adapter is installed. So if you are using >> forcedeth then you are really telling chipset what to do. Chipset >> translates your order and tells adapter what you want. Using forcedeth >> you are not talking to adapter directly but only to nForce chipset. > > forcedeth is a driver for the nvidia MAC. It doesn't really matter much > which PHY is connected outside the chipset to provide the actual port, > since that is mostly generic as far as the driver is concerned. > And this is what I've jus told using other words;) -- Registered Linux User 369908 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Asus A8V Deluxe, Xfree display problems with BIOS 1011
On Mon, May 09, 2005 at 10:30:38PM +0200, Joerg Rossdeutscher wrote:
> No, he quoted my mail, I just didn't post that very long part into the
> list. It just would make it even more ridiculous ("I have an Asus K8V
> deluxe..." "What board do you have?")
if grep "Bios.*update.*problem" inputdata; then
send "Bios repair procedures FAQ";
fi
Did you actually think a person read it? :)
I wonder if the person dealing with the message knows the same language
as you.
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Asus A8V Deluxe, Xfree display problems with BIOS 1011
Am Montag, den 09.05.2005, 19:12 + schrieb Jean-Luc Coulon (f5ibh):
> Le 09.05.2005 20:55:17, Joerg Rossdeutscher a écrit :
> > > And if your bios chipset is corrupt ,the main boot block of bios is
> > > damaged ,
> > Crazy.
> >
> > The problem is: Their bios breaks the nvidia drivers. And these guy
> > tells me something about broken eeproms and flashing the wrong bios.
>
> Yes really crazy.
> In your case, probably you got the answer for the question of an other
> guy...
No, he quoted my mail, I just didn't post that very long part into the
list. It just would make it even more ridiculous ("I have an Asus K8V
deluxe..." "What board do you have?")
Bye, Ratti
--
-o) fontlinge | Fontmanagement for Linux | Schriftenverwaltung in Linux
/\\ http://freshmeat.net/projects/fontlinge/
_\_V http://www.gesindel.de https://sourceforge.net/projects/fontlinge/
signature.asc
Description: This is a digitally signed message part
Re: glx for ia32 applications does not work
Alexander Fieroch kiedys napisal: > Hello, > > I've no problems starting 64bit glx applications like glxgears, but > starting glxgears in ia32 chroot I get a "Segmentation fault". > Starting doom3 in ia32 chroot I get the following error: > > [...] > - Initializing Sound System -- > sound system initialized. > -- > - R_InitOpenGL - > Setup X display connection > dlopen(libGL.so.1) > Initializing OpenGL display > Using XFree86-VidModeExtension Version 2.2 > DGA DirectVideo Mouse (Version 2.0) initialized > Free86-VidModeExtension Activated at 1280x1024 > Using 8/8/8 Color bits, 8 Alpha bits, 24 depth, 8 stencil display. > signal caught: Segmentation fault > si_code 1 > Trying to exit gracefully.. > idRenderSystem::Shutdown() > Fatal X Error: > Major opcode of failed request: 105 > Minor opcode of failed request: 0 > Serial number of failed request: 42 > BadValue (integer parameter out of range for operation) > > > The homepage of idsoftware sais: > "There are no amd64 builds planned at this time. However the 32 bit > binaries will run in a native amd64 environement." > > > But with native 64bit debian I get the same error. > My chroot is a complete debian 32 bit system where I've got no problems. > > I have installed nvidia-glx, nvidia-glx-ia32 and nvidia-kernel* and I'm > running a kernel (2.6.11.7) with enabled ia32_emulation. > So what's the problem? > > Thanks & regards, > Alexander > > > A I remember Doom was the only game with this problem. I have juzt upgraded glibc and generated new cache for libs (also I didn't used chroot command itself to run Doom of course;)) -- Registered Linux User 369908 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
isdn problem
hi! ive got a avm fritz card pci v1 and x86_64 linux installed but everytime i try to dial ippp0 there is an error like this: fcpcipnp0,ch0 cause E001B isdn_net: local hangup ippp0 ippp0: Chargesum is 0 i know that everything is configured well and the card works well under microshit win... anyone knows an answer to this problem??? thank you muHum ps: i have kernel 2.8.11 from standard 128mb netinstall iso and use isdnutils package
[SOLVED] Re: Realplayer in 32 chroot no sound
Hi Christan, > > I use ALSA as Soundsystem and have a snd_inte8x0 module in use. In 64 > > bit everything works out well. I have a selfcompiled vanilla kernel and > > compiled 32bit Soundemulation as Module. > > > > Do you have an hints? > > Check if all necessary devices were made in /dev/ and if you have the > right permissions e.g. if your user is in group "audio" inside the chroot, > too. Oh, I added my user to group audio and it worked out. thx a lot! Tobi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Asus A8V Deluxe, Xfree display problems with BIOS 1011
Le 09.05.2005 20:55:17, Joerg Rossdeutscher a écrit : Hi, Am Mittwoch, den 04.05.2005, 15:41 + schrieb Jean-Luc Coulon (f5ibh): > I've asked Asus support, the reply (In French) is that "they have no > UNIX/linux support for the moment, sorry for the inconvenient". I've also contacted Asus. The answer I got today is... bizzare: > Dear Friend : > Thank you for contacting ASUS Customer Service. > My name is and I would be assisting you today > > Sir, What's the motherboard do you have ? A8V deluxe ? K8V deluxe ? or > K8V ? do you have use other motherboard bios (eg , k8v deluxe) to > update A8V deluxe . Thanks a lot for your information . by the way , > you don't use other motherboard bios to update this motherboard . Or > it will kill your bios chipset . > > And if your bios chipset is corrupt ,the main boot block of bios is > damaged , > > so you can not re-flash it back because the system won't boot . > > if you have a eeprom programmer you can use it to write bios chip > back ; > > If you have another ASUS board( same type and same PCB version) ,you > can use "hot-swap" method to write bios back . > > > if above 2 ways are all impossible ,you need contact your mother board > dealer to send this faulty board to! repaired . > > > > Best regards ! Crazy. The problem is: Their bios breaks the nvidia drivers. And these guy tells me something about broken eeproms and flashing the wrong bios. Yes really crazy. Some guys do "hot swap" of EEPROM from one motherboard to an other one when they have broken the BIOS in such a way they can't flash it back. I've read some guys doing so from one motherbord to an other model. It seeems to work but you ahve to keep the motherboard powered while doing so and the EEPROM have to be the same model. In your case, probably you got the answer for the question of an other guy... Rated zero. Of course Bye, Ratti Jean-Luc pgpS02eXGNtzC.pgp Description: PGP signature
glx for ia32 applications does not work
Hello, I've no problems starting 64bit glx applications like glxgears, but starting glxgears in ia32 chroot I get a "Segmentation fault". Starting doom3 in ia32 chroot I get the following error: [...] - Initializing Sound System -- sound system initialized. -- - R_InitOpenGL - Setup X display connection dlopen(libGL.so.1) Initializing OpenGL display Using XFree86-VidModeExtension Version 2.2 DGA DirectVideo Mouse (Version 2.0) initialized Free86-VidModeExtension Activated at 1280x1024 Using 8/8/8 Color bits, 8 Alpha bits, 24 depth, 8 stencil display. signal caught: Segmentation fault si_code 1 Trying to exit gracefully.. idRenderSystem::Shutdown() Fatal X Error: Major opcode of failed request: 105 Minor opcode of failed request: 0 Serial number of failed request: 42 BadValue (integer parameter out of range for operation) The homepage of idsoftware sais: "There are no amd64 builds planned at this time. However the 32 bit binaries will run in a native amd64 environement." But with native 64bit debian I get the same error. My chroot is a complete debian 32 bit system where I've got no problems. I have installed nvidia-glx, nvidia-glx-ia32 and nvidia-kernel* and I'm running a kernel (2.6.11.7) with enabled ia32_emulation. So what's the problem? Thanks & regards, Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question
On Mon, May 09, 2005 at 08:12:44PM +0200, Marcin D?bicki wrote: > I just wanted to say that the primary adapter I call this device is a device > like Marvell Yukon (not Yukon) but nForce has an API used to hide real > interface from OS. True adapter driver is on nvidia chipset because only > chipset sees what adapter is installed. So if you are using forcedeth then > you are really telling chipset what to do. Chipset translates your order > and tells adapter what you want. Using forcedeth you are not talking to > adapter directly but only to nForce chipset. forcedeth is a driver for the nvidia MAC. It doesn't really matter much which PHY is connected outside the chipset to provide the actual port, since that is mostly generic as far as the driver is concerned. The mervall Yukon is another MAC chip (possibly with an internal PHY, I don't know) which uses a completely different driver (sk98lin). An ethernet port consists of a MAC, a PHY, and in the case of copper ethernet, some magnetics and the port. nvidia provides just the MAC, and nothing else. Many boards use some realtek PHY together with the nvidia MAC to build the ethernet port. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Asus A8V Deluxe, Xfree display problems with BIOS 1011
Hi, Am Mittwoch, den 04.05.2005, 15:41 + schrieb Jean-Luc Coulon (f5ibh): > I've asked Asus support, the reply (In French) is that "they have no > UNIX/linux support for the moment, sorry for the inconvenient". I've also contacted Asus. The answer I got today is... bizzare: > Dear Friend : > Thank you for contacting ASUS Customer Service. > My name is and I would be assisting you today > > Sir, What's the motherboard do you have ? A8V deluxe ? K8V deluxe ? or > K8V ? do you have use other motherboard bios (eg , k8v deluxe) to > update A8V deluxe . Thanks a lot for your information . by the way , > you don't use other motherboard bios to update this motherboard . Or > it will kill your bios chipset . > > And if your bios chipset is corrupt ,the main boot block of bios is > damaged , > > so you can not re-flash it back because the system won't boot . > > if you have a eeprom programmer you can use it to write bios chip > back ; > > If you have another ASUS board( same type and same PCB version) ,you > can use "hot-swap" method to write bios back . > > > if above 2 ways are all impossible ,you need contact your mother board > dealer to send this faulty board to! repaired . > > > > Best regards ! Crazy. The problem is: Their bios breaks the nvidia drivers. And these guy tells me something about broken eeproms and flashing the wrong bios. Rated zero. Bye, Ratti -- -o) fontlinge | Fontmanagement for Linux | Schriftenverwaltung in Linux /\\ http://freshmeat.net/projects/fontlinge/ _\_V http://www.gesindel.de https://sourceforge.net/projects/fontlinge/ signature.asc Description: This is a digitally signed message part
Re: Bug#308003: FTBFS: cannot find -lc (forwarded from Andreas Jochens)
Harald Dunkel <[EMAIL PROTECTED]> writes: > Goswin von Brederlow wrote: >> >> Version 1.3 was broken, version 1.4 is fixed. Please upgrade. >> > > Still no change: > > [EMAIL PROTECTED]:harri 1003} ls -lhd /usr/lib32 > ls: /usr/lib32: No such file or directory > [EMAIL PROTECTED]:harri 1003} apt-get install ia32-libs > Reading Package Lists... Done > Building Dependency Tree... Done > The following extra packages will be installed: > lib32gcc1 libc6-i386 > The following NEW packages will be installed: > ia32-libs lib32gcc1 libc6-i386 > 0 upgraded, 3 newly installed, 0 to remove and 14 not upgraded. > Need to get 0B/6366kB of archives. > After unpacking 15.7MB of additional disk space will be used. > Do you want to continue? [Y/n] y > Selecting previously deselected package lib32gcc1. > (Reading database ... 63422 files and directories currently installed.) > Unpacking lib32gcc1 (from .../lib32gcc1_4.0.0-2_amd64.deb) ... > Selecting previously deselected package libc6-i386. > Unpacking libc6-i386 (from .../libc6-i386_2.3.5-1_amd64.deb) ... > Selecting previously deselected package ia32-libs. > Unpacking ia32-libs (from .../ia32-libs_1.4.0.0.1.gcc4_amd64.deb) ... > Setting up lib32gcc1 (4.0.0-2) ... > Setting up libc6-i386 (2.3.5-1) ... > > Setting up ia32-libs (1.4.0.0.1.gcc4) ... > > [EMAIL PROTECTED]:harri 1003} ls -lhd /usr/lib32 > drwxr-xr-x 5 root root 2.2K May 9 19:49 /usr/lib32 > > > Regards > > Harri Well, that is the gcc4 repository then. [EMAIL PROTECTED]:~% dpkg -c /mnt/mirror/ivanova/debian/pool/main/g/gcc-3.4/lib32gcc1_3.4.3-12.1_amd64.deb drwxr-xr-x root/root 0 2005-05-04 17:25:03 ./ drwxr-xr-x root/root 0 2005-05-04 17:25:02 ./usr/ drwxr-xr-x root/root 0 2005-05-04 17:25:02 ./usr/share/ drwxr-xr-x root/root 0 2005-05-04 17:25:02 ./usr/share/doc/ drwxr-xr-x root/root 0 2005-05-04 17:25:03 ./usr/share/doc/lib32gcc1/ -rw-r--r-- root/root 26669 2005-05-04 13:53:56 ./usr/share/doc/lib32gcc1/copyright -rw-r--r-- root/root 52516 2005-05-04 13:53:56 ./usr/share/doc/lib32gcc1/changelog.Debian.gz drwxr-xr-x root/root 0 2005-05-04 17:25:02 ./emul/ drwxr-xr-x root/root 0 2005-05-04 17:25:02 ./emul/ia32-linux/ drwxr-xr-x root/root 0 2005-05-04 17:25:02 ./emul/ia32-linux/usr/ drwxr-xr-x root/root 0 2005-05-04 17:25:02 ./emul/ia32-linux/usr/lib/ -rw-r--r-- root/root 31612 2005-05-04 17:25:02 ./emul/ia32-linux/usr/lib/libgcc_s.so.1 I guess you have /usr/lib32 in the lib32gcc1_4.0.0-2_amd64.deb. That won't work. ia32-libs and lib32gcc1 have to work together on that. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question
Lennart Sorensen kiedys napisal: > On Sat, May 07, 2005 at 07:41:06PM +0200, Marcin D?bicki wrote: >> I have nForce 3 250 chipset for now and I really have no idea what nForce >> Network Adapter it is. Probably a kind of Marvell (and I use forcedeth >> for it). Also as a secondary there is Marvell Yukon which works fine with >> sk98lin. While using sk98lin it sees only Yukon. >> The strange thing is that most Marvell's used with nForce can be run with >> sk98lin but there is a group of a few adapters which can work only with >> forcedeth or original nForce drivers. > > forcedeth runs the network MAC built into the nvidia chipset. It is of > no relation to the Marvell Yukon, which is a gigabit chip that is > popular as an add on chip, which certainly Asus likes to include on many > boards. > > For example the A7N8X-E-DX has a 10/100 nforce network port and a > gigabit marvell yukon port. I believe many of the K8 nforce boards are > made the same way. > > The A8V-DX has just a marvell yukon, but of course that is a via chipset > so it never would have anything nvidia in the first place. :) > > sk98lin will run the Yukon, and forcedeth will run the nforce chip. > Which driver you need depends entirely on which MAC the board maker > decided to use (the builtin, an add on marvell, or both if using two > ports). Boards with PCIe seem to have trouble with the sk98lin driver > currently in the kernel for some reason when using the marvell. I just wanted to say that the primary adapter I call this device is a device like Marvell Yukon (not Yukon) but nForce has an API used to hide real interface from OS. True adapter driver is on nvidia chipset because only chipset sees what adapter is installed. So if you are using forcedeth then you are really telling chipset what to do. Chipset translates your order and tells adapter what you want. Using forcedeth you are not talking to adapter directly but only to nForce chipset. > >> As i see there could be an explanation for it. Promary adapter is >> communicating with OS via chipset while secondary isn't (that is on >> nForce scheme's). So the explanation is that primary adapter is driven by >> chipset intarface which is working with forcedeth (and that interface is >> the same or almost the same for every nForce2/3/4 chipset). >> It everything is on net (pictures describing my nForce3 architecture are >> in manual for my motherboard). The conclusion is that when you are trying >> to get help for Marvell you must write if it is secondary or primary >> adapter on you mobo. >> Of course there is an issue that some secondary Marvell adapters works >> with forcedeth whil should with sk98lin. And tah thing is strange > > The primary isn't always using the internal nforce controller. > Sometimes the nforce controller isn't enabled at all (maybe nvidia ships > chipsets without that feature at reduced cost). > > Len Sorensen > Yes, some are with disabled internal adapter but it is not very often situation. And if it is then nvidia doesn't cut the adapter from chipset but onli disables it -- Registered Linux User 369908 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
netinstall : no module
The install seem to have no module for my networks cards (nvidia Gigabit or/and via-rhine II). Where I can find 64 bits drivers for them ? thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#308003: FTBFS: cannot find -lc (forwarded from Andreas Jochens)
Goswin von Brederlow wrote: > > Version 1.3 was broken, version 1.4 is fixed. Please upgrade. > Still no change: [EMAIL PROTECTED]:harri 1003} ls -lhd /usr/lib32 ls: /usr/lib32: No such file or directory [EMAIL PROTECTED]:harri 1003} apt-get install ia32-libs Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: lib32gcc1 libc6-i386 The following NEW packages will be installed: ia32-libs lib32gcc1 libc6-i386 0 upgraded, 3 newly installed, 0 to remove and 14 not upgraded. Need to get 0B/6366kB of archives. After unpacking 15.7MB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously deselected package lib32gcc1. (Reading database ... 63422 files and directories currently installed.) Unpacking lib32gcc1 (from .../lib32gcc1_4.0.0-2_amd64.deb) ... Selecting previously deselected package libc6-i386. Unpacking libc6-i386 (from .../libc6-i386_2.3.5-1_amd64.deb) ... Selecting previously deselected package ia32-libs. Unpacking ia32-libs (from .../ia32-libs_1.4.0.0.1.gcc4_amd64.deb) ... Setting up lib32gcc1 (4.0.0-2) ... Setting up libc6-i386 (2.3.5-1) ... Setting up ia32-libs (1.4.0.0.1.gcc4) ... [EMAIL PROTECTED]:harri 1003} ls -lhd /usr/lib32 drwxr-xr-x 5 root root 2.2K May 9 19:49 /usr/lib32 Regards Harri signature.asc Description: OpenPGP digital signature
Re: g++ compile failure
Mario <[EMAIL PROTECTED]> writes: > Hi everyone! > > I'm trying to compile the source added below, which works on many other > systems (32 Bit SuSE and Debian, 64Bit SuSE) but not with debian-amd64. > > My current compiler says the following, but the problem has been present in > amd64-pure64 repository since I started using debian-amd64 many month ago. > > g++ -v > Reading specs from /usr/lib/gcc-lib/x86_64-linux/3.3.6/specs > Configured with: ../src/configure -v > --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr > --mandir=/usr/share/man --infodir=/usr/share/info > --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared > --enable-__cxa_atexit --with-system-zlib --enable-nls > --without-included-gettext --enable-clocale=gnu --enable-debug > --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc > --disable-multilib x86_64-linux > Thread model: posix > gcc version 3.3.6 (Debian 1:3.3.6-3) > > g++ main.cpp -c -o main.o > # compiler works with 97% CPU Load and 96MB virtual memory > # but does not stop compiling > > The piece of code I'm trying to compile is: > > code > #include "boost/spirit/core.hpp" Include that manually and reduce further plaese. For a gcc bugreport you should use the preprocessed files. Also please try with g++-3.4. If that fixes it already there is probably nothing left to do but wait. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: g++ compile failure
if you want people to test, then this is missing. > boost/spirit/core.hpp I suspect, however, you would be beter off on the gcc list. amd64 is officially supported there. Cheers, Ernest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pinfo -- release critical bug for amd64
[EMAIL PROTECTED] (Bob Proulx) writes: >> > At the time it seemed reasonable to wait for the maintainer to react >> > to the bug and to upload a fixed version. After 113 days that does >> > not seem to be going to happen in time for sarge. > > Okay, so we are still left with what to do about this problem. What > is the solution? It is a bug that can potentially cause FTBFS on any > given architecture. Certainly the .deb package built for amd64 has > hit this problem. > > However I downloaded the .deb file for every Debian supported > architecture and all of them apparently built without hitting this > problem. It looks like amd64 just came up lucky. This was probably > also helped along by the fact that the other systems build on > filesystems with one second resolutions but I am guessing that amd64 > built on a filesystem with microsecond resolution. Any architecture with 2.6 kernel and enough ram. The internal timestamps have mikrosecond resolution while the on disk timestamps only seconds. I think amd64 is the only arch having 2.6.x on the buildd so far. > Because we want amd64 to stay in sync with Debian sarge as much as > possible I still propose that the package be re-queued to build again. > The odds are reasonable that it will build correctly regardless of > this package filestamp bug. Then we will have a good working package > for amd64 and will remain in sync with sarge. And there is still the > bug against the mainstream Debian package so this bug won't get lost. > > Sound good? > > Bob The right thing to do is to add a "touch doc/pinfo.info" to debian rules or add a Build-Depends on makeinfo and NMU it. We know what is wrong, we know a trivial way to fix it. Why should we compromise? pinfo should be fixed or removed from sarge. I made the bug RC so the release team should do the right thing now. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
g++ compile failure
Hi everyone!
I'm trying to compile the source added below, which works on many other
systems (32 Bit SuSE and Debian, 64Bit SuSE) but not with debian-amd64.
My current compiler says the following, but the problem has been present in
amd64-pure64 repository since I started using debian-amd64 many month ago.
g++ -v
Reading specs from /usr/lib/gcc-lib/x86_64-linux/3.3.6/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
--enable-__cxa_atexit --with-system-zlib --enable-nls
--without-included-gettext --enable-clocale=gnu --enable-debug
--enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc
--disable-multilib x86_64-linux
Thread model: posix
gcc version 3.3.6 (Debian 1:3.3.6-3)
g++ main.cpp -c -o main.o
# compiler works with 97% CPU Load and 96MB virtual memory
# but does not stop compiling
The piece of code I'm trying to compile is:
code
#include "boost/spirit/core.hpp"
using namespace boost::spirit;
char * begin;
char * end;
void test()
{
unsigned int ui;
parse_info<> info = boost::spirit::parse( begin, end, uint_p[assign(ui)],
space_p );
}
end code
Remark: That code does not make any sense but is the smallest subset of code I
could extract that produces the failure on my system.
Any hints about what goes wrong here?
Mario
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OT- BBC "coverage" of Win Longhorn launch
On Sun, May 08, 2005 at 03:24:22AM -0300, Javier Kohen wrote: > Nice catch. Note that there is a "contact us" link in the same page that > you can use to let the BBC 'producers' know about the missing > information. Maybe if several of us let them know they'll write an > article on Linux/AMD64 or something. So if 64bit chips have been around since the 90s, and windows is only going 64bit now, what were they doing? Oh you mean those 64bit chips had 64bit software since they were alpha and sparc and ran true64, linux, solaris and whatever other 64bit unix they wanted. Seems pretty irrelevant when 64bit chips came out, unless it is one you would want to run windows on (I guess they never got 64bit windows on the alpha did they). What matters is when the 64bit x86 came out, which is still a while ago. I guess windows isn't written as cleanly (type wise) as it ought to have been. :) I also don't believe anything video related will run 1000 times faster on 64bit than 32bit. Nor do I believe 64bit makes things more secure than 32bit, unless having to cleanup all the type sizes meant they had to fix their code. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Mozart for amd64
Hi, I am the maintainer of the Mozart/Oz package. http://packages.debian.org/unstable/devel/mozart I am also one of the upstream developers. This software doesn't currently build on any of the 64 bit architectures and making it do so will, I think, be a bit hairy and quite a bit of work. Unfortunately, I don't have access to any shiny 64 bit hardware. Can anyone offer me an account a debian amd64 environment so that I can investigate this further? I don't know how long this will take me. Also, I am not a DD :-(. thanks for any help, Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#308003: FTBFS: cannot find -lc (forwarded from Andreas Jochens)
Harald Dunkel <[EMAIL PROTECTED]> writes: > Unpacking ia32-libs (from .../ia32-libs_1.3.0.0.1.gcc4_amd64.deb) ... > Setting up lib32gcc1 (4.0.0-1) ... > Setting up ia32-libs (1.3.0.0.1.gcc4) ... Version 1.3 was broken, version 1.4 is fixed. Please upgrade. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question
On Sat, May 07, 2005 at 07:41:06PM +0200, Marcin D?bicki wrote: > I have nForce 3 250 chipset for now and I really have no idea what nForce > Network Adapter it is. Probably a kind of Marvell (and I use forcedeth for > it). Also as a secondary there is Marvell Yukon which works fine with > sk98lin. While using sk98lin it sees only Yukon. > The strange thing is that most Marvell's used with nForce can be run with > sk98lin but there is a group of a few adapters which can work only with > forcedeth or original nForce drivers. forcedeth runs the network MAC built into the nvidia chipset. It is of no relation to the Marvell Yukon, which is a gigabit chip that is popular as an add on chip, which certainly Asus likes to include on many boards. For example the A7N8X-E-DX has a 10/100 nforce network port and a gigabit marvell yukon port. I believe many of the K8 nforce boards are made the same way. The A8V-DX has just a marvell yukon, but of course that is a via chipset so it never would have anything nvidia in the first place. :) sk98lin will run the Yukon, and forcedeth will run the nforce chip. Which driver you need depends entirely on which MAC the board maker decided to use (the builtin, an add on marvell, or both if using two ports). Boards with PCIe seem to have trouble with the sk98lin driver currently in the kernel for some reason when using the marvell. > As i see there could be an explanation for it. Promary adapter is > communicating with OS via chipset while secondary isn't (that is on nForce > scheme's). So the explanation is that primary adapter is driven by chipset > intarface which is working with forcedeth (and that interface is the same > or almost the same for every nForce2/3/4 chipset). > It everything is on net (pictures describing my nForce3 architecture are in > manual for my motherboard). The conclusion is that when you are trying to > get help for Marvell you must write if it is secondary or primary adapter > on you mobo. > Of course there is an issue that some secondary Marvell adapters works with > forcedeth whil should with sk98lin. And tah thing is strange The primary isn't always using the internal nforce controller. Sometimes the nforce controller isn't enabled at all (maybe nvidia ships chipsets without that feature at reduced cost). Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing 2.6 kernel
Hello, On Mon, May 09, 2005 at 05:59:17AM -0700, Attila Kocsis wrote: > Can I choose before (or during) the installation of 64 > bit sarge whether I wanna use 2.6 or 2.4 kernel? > If yes, when and how? You can install only a 2.6 kernel, because debian-amd64 does not support 2.4 kernels at all. The system won't even boot with a 2.4 kernel. AMD64 support is limited in 2.4 kernels, thus there are no kernel-images provided. Additionally, the amd64 libc6 needs a kernel supporting NPTL and TLS, both not available in vanilla 2.4 kernels. Kind regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
installing 2.6 kernel
Hi, Can I choose before (or during) the installation of 64 bit sarge whether I wanna use 2.6 or 2.4 kernel? If yes, when and how? Thank you __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: VMware
On Sat, May 07, 2005 at 05:34:43PM -0800, Greg Madden wrote: > AFAIKT from the VMware site, VMware supports specific versions of > distros/kernels. It is ambiguous, at least to me, to say they support > 64bit when they say they support i.e. SUSE Linux Enterprise Server 8 - > stock 2.4.19, 64-bit. Suse includes the ia32-libs so does this mean > VMware will run on a pure64 OS or only one with the appropriate 32 bit > libraries loaded. As far as I know, one with 32bit libs installed. It does support 64bit kernels in version 5 (and 4.5 with update patches) as host, which matters since vmware does use kernel modules for some of its work. A number of people have run it on debian just fine, and I believe all they needed was the 32bit libs installed, and to run the installer in 64bit mode (since it has to build 64bit kernel modules). Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Realplayer in 32 chroot no sound
Hi On 2005-05-09 Tobias Krais wrote: > I use ALSA as Soundsystem and have a snd_inte8x0 module in use. In 64 > bit everything works out well. I have a selfcompiled vanilla kernel and > compiled 32bit Soundemulation as Module. > > Do you have an hints? Check if all necessary devices were made in /dev/ and if you have the right permissions e.g. if your user is in group "audio" inside the chroot, too. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#308003: FTBFS: cannot find -lc (forwarded from Andreas Jochens)
On lun, 2005-05-09 at 05:47 +0200, Goswin von Brederlow wrote: > Please make sure you have: > > [EMAIL PROTECTED]:~% ls -lhd /usr/lib32 > lrwxrwxrwx 1 root root 24 2005-05-08 20:01 /usr/lib32 -> > /emul/ia32-linux/usr/lib/ Thank you for the hint ! My system was messed up, indeed. I fixed it and it solved the problem. Therefore I'm closing this bug. The build is not finished yet (it takes ages), but if there is another problem, I'll open another bug... BTW, my system has this line in /etc/apt/sources.list: deb http://ftp.de.debian.org/debian-amd64/debian/ experimental main contrib but gcc-4.0 is not available. I'm wondering which packages Andreas Jochens is using to report all the build failures in Debian packages with gcc-4.0. Thanks again, -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Realplayer in 32 chroot no sound
Hi together, I have a 64 bit Debian installed and a 32 bit chroot for OOffice and now also for Realplayer. Realplayer works very well, but I do not hear any Sound. I use ALSA as Soundsystem and have a snd_inte8x0 module in use. In 64 bit everything works out well. I have a selfcompiled vanilla kernel and compiled 32bit Soundemulation as Module. Do you have an hints? Greetings, Tobias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
