Re: more weird apt - bzip2.

[Bob Proulx]

Chris Wakefield wrote:
> My system is sick.   For a month now, I haven't been able to successfully 
> update or upgrade, now  I can't install anything at all now:
> Can anyone suggest some kind of fix?
> ...
> Preparing to replace bzip2 1.0.2-8 (using .../bzip2_1.0.2-8_amd64.deb) ...
> /var/lib/dpkg/info/bzip2.prerm: line 7:  6745 Illegal instruction 
> install-docs -r bzip2
> dpkg: warning - old pre-removal script returned error exit status 132

Hmm...  'install-docs' is a perl script.  Is perl working on your
system?

  perl -e 0
  install-docs

Neither of those should have any output.  So errors from those may
point to something.  The following should list some status output.

  install-docs -s bzip2

But doc-base is not required to be installed.  If the problem is
something with doc base and not perl then I would try removing it.
There are some packages that depend upon it so we should use apt to
remove those too, if that seems reasonable.

  apt-get remove doc-base

Or if that fails because of the current problem:

  dpkg --remove doc-base

I am guessing something is wrong with perl on your system and
reinstalling it might be best.  But you will probably have to clear
your current problem first.

Bob


signature.asc
Description: Digital signature

more weird apt - bzip2.

[Chris Wakefield]

HI all.

My system is sick.   For a month now, I haven't been able to successfully 
update or upgrade, now  I can't install anything at all now:
Can anyone suggest some kind of fix?

_

# apt-get install digikam
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  libimlib2-dev libkexif1 libkipi0 libltdl3-dev libtiff4-dev libtiffxx0c2 
libungif4-dev
Suggested packages:
  libtool-doc
Recommended packages:
  digikamimageplugins kipi-plugins
The following packages will be REMOVED:
  libtiffxx0
The following NEW packages will be installed:
  digikam libimlib2-dev libkexif1 libkipi0 libltdl3-dev libtiff4-dev 
libtiffxx0c2 libungif4-dev
0 upgraded, 8 newly installed, 1 to remove and 22 not upgraded.
1 not fully installed or removed.
Need to get 12.6MB/12.9MB of archives.
After unpacking 21.5MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://debian.csail.mit.edu sid/main libkexif1 0.2.1-2 [42.7kB]
Get:2 http://debian.csail.mit.edu sid/main libkipi0 0.1.1-2 [122kB]
Get:3 http://debian.csail.mit.edu sid/main libtiffxx0c2 3.7.3-1 [42.2kB]
Get:4 http://debian.csail.mit.edu sid/main libtiff4-dev 3.7.3-1 [280kB]
Get:5 http://debian.csail.mit.edu sid/main libungif4-dev 4.1.3-3 [41.2kB]
Get:6 http://debian.csail.mit.edu sid/main libltdl3-dev 1.5.6-6 [19.2kB]
Get:7 http://debian.csail.mit.edu sid/main libimlib2-dev 1.2.0-2.2 [613kB]
Get:8 http://debian.csail.mit.edu sid/main digikam 0.7.2-4 [11.5MB]
Fetched 12.6MB in 22s (551kB/s)
/bin/sh: line 1:  6735 Illegal instruction /usr/sbin/dpkg-preconfigure 
--apt
(Reading database ... 143861 files and directories currently installed.)
Preparing to replace bzip2 1.0.2-8 (using .../bzip2_1.0.2-8_amd64.deb) ...
/var/lib/dpkg/info/bzip2.prerm: line 7:  6745 Illegal instruction 
install-docs -r bzip2
dpkg: warning - old pre-removal script returned error exit status 132
dpkg - trying script from the new package instead ...
/var/lib/dpkg/tmp.ci/prerm: line 7:  6747 Illegal instruction install-docs 
-r bzip2
dpkg: error processing /var/cache/apt/archives/bzip2_1.0.2-8_amd64.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 132
/var/lib/dpkg/info/bzip2.postinst: line 16:  6749 Illegal instruction 
install-info --quiet --section "General Commands" "General 
Commands" /usr/share/info/bzip2.info
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 132
Errors were encountered while processing:
 /var/cache/apt/archives/bzip2_1.0.2-8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

SuperMicro H8DCE motherboard

[Samat Jain]

Hello,

I've been running Debian 3.1 for AMD64 for a few weeks now, and have just 
wanted to report that it is working (for the most part) so that it can be 
added to the supported K8 mainboards list.

Mainboard name:
SuperMicro H8DCE

ATA:
unsure, don't use it, presumably working

Serial ATA:
sata_nv

Network:
forcedeth

Sound:
unsure, don't use it, presumably working

-- 
Samat Jain 

Machines have less problems. I'd like to be a machine.
-- Andy Warhol (137)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mp3 encoding - lame?

[Corey Hickey]

jurriaan wrote:
> I did run memtest86 after overclocking, no problems during a 24 hrs
> period. The I compiled 250 kernels, which were all identical. Still,
> lame is obviously very sensitive.
> The moral of the story: overclocking a 3700 San Diego to 2750 MHz works
> most of the time, but not with lame. For now, 2640 works a lot better.
> 
> 
>>- Check to make sure your system is being cooled adequately.
> 
> 
> the cpu is never above 45 degrees C.
> 
>>- Run memtest86 and see if it likes your RAM.
> 
> 
> 24 hrs - no problems.
> 
> This must sound lame, but I really thought I had it stable, with memtest
> and compiling kernels.

No, it's only LAME once you get it working right. :)

Kernel compilation might not be so good a test since it's heavy in I/O
-- your CPU isn't working as much while it's waiting for the hard disk
and cools down somewhat. I've mostly used mencoder for stability testing
in the past. Burnk7 (from the i386 cpuburn package) is very good for
heating up the CPU, though, and I might start using that instead of
mencoder. Bzip2 seems to work well for testing overclocked RAM, but I
try to stay away from that.

-Corey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mp3 encoding - lame?

[jurriaan]

From: Corey Hickey <[EMAIL PROTECTED]>
Date: Sun, Aug 21, 2005 at 11:45:44AM -0700
X-XS4All-To: 
> jurriaan wrote:
> > 
> > This is with my own gcc-4.0 compiled lame. Sometimes it hangs, most of
> > the time it crashes on this file. AFAIK the .wav file is OK, it plays
> > and is a decompressed .flac file. It's 5.8 MiB, btw.
> 
> Are you saying that your lame behaves differently if you run it multiple
> times on the same file? If that is the case you almost certainly have
> faulty or overheating hardware.
> 
> - If you're overclocking, don't do so as much.

I did run memtest86 after overclocking, no problems during a 24 hrs
period. The I compiled 250 kernels, which were all identical. Still,
lame is obviously very sensitive.
The moral of the story: overclocking a 3700 San Diego to 2750 MHz works
most of the time, but not with lame. For now, 2640 works a lot better.

> - Check to make sure your system is being cooled adequately.

the cpu is never above 45 degrees C.
> - Run memtest86 and see if it likes your RAM.

24 hrs - no problems.

This must sound lame, but I really thought I had it stable, with memtest
and compiling kernels.

Thanks,
Jurriaan
-- 
Corporal... get me the cassette of Spaceballs: The Movie.
Debian (Unstable) GNU/Linux 2.6.13-rc4-mm1 5286 bogomips load 0.44


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mp3 encoding - lame?

[Corey Hickey]

jurriaan wrote:
> Script started on Sun 21 Aug 2005 02:49:45 PM CEST
> INTEL :cat test.in
> file /usr/local/bin/lame
> r --vbr-new -V 0 "18 US Forces.wav"
> bt
> INTEL :rm *mp3; gdb < test.in
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0045224b in quantize_x34 ()
> (gdb) #0  0x0045224b in quantize_x34 ()
> #1  0x00456cdb in VBR_noise_shaping ()
> #2  0x0044d888 in VBR_iteration_loop ()
> #3  0x00443abb in lame_encode_mp3_frame ()
> #4  0x0040f126 in lame_encode_buffer_sample_t ()
> #5  0x004104e7 in lame_encode_buffer_int ()
> #6  0x00402a6e in lame_encoder ()
> #7  0x00403763 in main ()
> 
> This is with my own gcc-4.0 compiled lame. Sometimes it hangs, most of
> the time it crashes on this file. AFAIK the .wav file is OK, it plays
> and is a decompressed .flac file. It's 5.8 MiB, btw.

Are you saying that your lame behaves differently if you run it multiple
times on the same file? If that is the case you almost certainly have
faulty or overheating hardware.

- If you're overclocking, don't do so as much.
- Check to make sure your system is being cooled adequately.
- Run memtest86 and see if it likes your RAM.

For what it's worth, my machine has no problem with your test file and
"--vbr-new -V 0". You can try my deb if you want, but I suspect your
problems are hardware-related.

http://fatooh.org/files/lame_3.96-0.1_amd64.deb

-Corey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

IEEE Cluster2005 Registration Online

[Cluster2005]

see http://cluster2005.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

IEEE Cluster2005 Registration Online

[Cluster2005]

see http://cluster2005.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problems with downloading Sarge

[Alan Ianson]

On Sat August 20 2005 11:46 pm, Master Millenium wrote:
> Now I have downloaded Sarge in full DVD sets with Jigdo and it says that
> there are 137 files missing. What should I do? Have someone else had the
> same problem? I have downloaded it from fi.debian.org.

I have to be more carefull what list I'm reading... That mirror (direct.ca) I 
told you about only has sarge i386. I got my sarge amd64 from here..

http://amd64.debian.net/debian-amd64/

Sorry for the mix up..


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problems with downloading Sarge

[Alan Ianson]

On Sat August 20 2005 11:46 pm, Master Millenium wrote:
> Now I have downloaded Sarge in full DVD sets with Jigdo and it says that
> there are 137 files missing. What should I do? Have someone else had the
> same problem? I have downloaded it from fi.debian.org.

I did the same thing a month or two ago and didn't have any problem. I would 
try running jigdo again and just change the mirror you are using. Jigdo will 
simply grab the files that are missing (if it can find them). I downloaded 
from http://mirror.direct.ca/linux/debian/ with good results.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Building an useful list to keep an eye on when migrating from i386

[Jonathan ILIAS]

Thanks to you and Lennart for this great help.

Now I've discovered stinkypete. By the way, anybody knows another amd64 
apt repository (unofficial) ?


--
Jonathan ILIAS
-==---==---==-
"Chaque homme a trois caracteres : celui qu'il a, celui qu'il montre
et celui qu'il croit avoir", Alphonse KARR


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Acer Turion laptops

[Frederik Schueler]

Hello,

On Sun, Aug 21, 2005 at 12:24:47PM +0200, Michelasso wrote:
> I would like to ask you again (maybe you didn't see my question) if
> you have any success in making the wireless card and the internal
> modem working

I didn't try to get wavelan to work at all, sorry.
But I tried with the modem, and had the same experience: loading the 
module does nothing, udev does not create any ttySx devices.

BTW, did you manage to get TV-out working? 

Best regards
Frederik Schueler

-- 
ENOSIG


signature.asc
Description: Digital signature

Re: illegal user logon

[Dr Gavin Seddon]

I assumed iptables,
thanks for the reply.
Gavin.

On Sat, 2005-08-20 at 16:23 -0400, Christopher Browne wrote:
> On 8/20/05, Dr Gavin Seddon <[EMAIL PROTECTED]> wrote:
> > I have noticed in my log there has been people trying to logon to my
> > debian box.  Is there any software available to stop this, or should I
> > use pam to restrict access?
> 
> This isn't likely to have any answers where AMD64 is particularly relevant.
> 
> In principle, you might try using ipchains/iptables to cease access to
> ports that access services that outsiders oughtn't access.
> 
> If they are trying plain old ssh, and there's a lot of password
> guessing going on, you might consider configuring it to accept only
> ssh keys for authentication.  That would doubtless add a certain
> inconvenience factor, but keep password guessing from being AT ALL
> effective as an attack...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Last dist-upgrade of sid breaks a little kde

[Ernest jw ter Kuile]

Hi, welcome to Unstable.

Best you can do is to downgrade kde to whatever is here (I believe this is for 
sarge) :

deb http://pkg-kde.alioth.debian.org/kde-3.4.1/ ./

note: you will need to downgrade some other packages as wel back to Sarge. 
Jack for one I know about, probably others too.

Don't dist-upgrade kde to sid for the next few days/weeks until kde is deemed 
safe again, or beter yet, only use testing, and wait until kde appears there.

> Is anybody experiencing the same problem?
yea, lots of peoples, just read around. Most of them on debian-qt-kde though.

> Any suggestions?

PEOPLE : DON"T USE UNSTABLE (SID) UNLESS YOU KEEP UP TO DATE WITH WHAT IS 
HAPPENNING AND KNOW HOW TO HANDLE THESE ERRORS !

Unstable is called exactly that because, ... wel, ... it is.

Ernest.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Last dist-upgrade of sid breaks a little kde

[hugelmopf]

If I am not mistaken, this is a known problem. Check debian-kde, for example 
here:
http://lists.debian.org/debian-kde/2005/08/msg00177.html


Michelasso <[EMAIL PROTECTED]> schrieb am 21.08.05 12:37:12:
> 
> Hello everybody,
> after last upgrade of sid (I am using only official repositories, I
> have decided to wait for kde 3.4 to come into unstable) my kde 3.3 has
> a problem: the applications list in the 'K' menu is empty, even if all
> applications are still here, and I can launch them form a shell. Also
> the applet I had installed on the panel are missing; I have tried to
> delete my .kde directory but nothing has changed. All relevant
> packages of kde seems to be installed, only some of them are held back
> due to missing dpendencies:
> 
> arts kdelibs kdelibs-bin kfocus kphone ksimus ksimus-boolean
> ksimus-floatingpoint
> 
> Is anybody experiencing the same problem?
> Any suggestions?
> TIA
> 


__
Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach!

Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Last dist-upgrade of sid breaks a little kde

[Michelasso]

Hello everybody,
after last upgrade of sid (I am using only official repositories, I
have decided to wait for kde 3.4 to come into unstable) my kde 3.3 has
a problem: the applications list in the 'K' menu is empty, even if all
applications are still here, and I can launch them form a shell. Also
the applet I had installed on the panel are missing; I have tried to
delete my .kde directory but nothing has changed. All relevant
packages of kde seems to be installed, only some of them are held back
due to missing dpendencies:

arts kdelibs kdelibs-bin kfocus kphone ksimus ksimus-boolean
ksimus-floatingpoint

Is anybody experiencing the same problem?
Any suggestions?
TIA

Re: Acer Turion laptops

[Michelasso]

On 8/18/05, Theodore Kisner <[EMAIL PROTECTED]> wrote:

> 
> Are you sure the button doesn't work?  On my compaq R3000 (athlon64) laptop,
> the button behaves differently with the 32bit windows driver and the 64bit
> one.  In 32bit debian with the 32bit windows driver under ndiswrapper,
> enabling the button turns on the wifi indicator light which then glows solid.
> With 64bit debian and the 64bit driver, pressing the button *does* change the
> state of the radio, but the indicator does not turn on.  When there is
> network traffic, the light flickers indicating traffic on the connection.
> 
> So basically if I can't find the network, I push the button and try again.
> Actually I usually just leave it enabled anyway.  Another thing you could try
> is to boot into windows, enable the radio, and then reboot into linux and see
> if that works...

I have tried both things, but the radio is always turned off; when I
press the button that should turn it on I get this in syslog:

 Aug 21 12:26:14 aquila kernel: atkbd.c: Unknown key pressed
(translated set 2, code 0xd6 on isa0060/serio0).
Aug 21 12:26:14 aquila kernel: atkbd.c: Use 'setkeycodes e056
' to make it known.
Aug 21 12:26:15 aquila kernel: atkbd.c: Unknown key released
(translated set 2, code 0xd6 on isa0060/serio0).
Aug 21 12:26:15 aquila kernel: atkbd.c: Use 'setkeycodes e056
' to make it known.

So the kernel doesn't recognize the button.
Bye.

Re: Acer Turion laptops

[Michelasso]

On 8/18/05, Frederik Schueler <[EMAIL PROTECTED]> wrote:
> Yeah, I did something similar, additionally the initscript does a
> 
> echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> 
> to make the fan shut up ;-)
> 
> 

Thanks a lot for your answer;
I would like to ask you again (maybe you didn't see my question) if
you have any success in making the wireless card and the internal
modem working: for the first one, I have problems with the button that
turns the radio on; for the second,I have compiled snd_atiixp_modem as
a module, but when I load it I see nothing in syslog and I cannot find
any device associated to the modem.

Bye.

Re: kbd problems

[valentina messeri]

Quoting daniele <[EMAIL PROTECTED]>:

> valentina messeri ha scritto:
> 
> >i'm running sid on this machine (I installed from sarge net-install):
> >
> >uname -a
> >Linux (none) 2.6.11-9-amd64-k8 #1 Wed Jun 29 17:33:01 CEST 2005 x86_64
> GNU/Linux
> >

> i remember when i used gentoo on amd64 and xorg i had some problem in 
> kde with xkb
> i had no problem in fluxbox
> i find in internet that the same problem is only in gnome and kde, not 
> in other window managers
> now i cannot hep you because i use sarge ;-)
> ciao

well, nor fluxbox neither (almost)all light windows manager works...i started
from there because i had had problems with keyboards with gnome in my former
machine version...problems I fixed installing xserver-xorg, then had hd/system
dead and reinstalling there was  no way to have keyboard working again

By the way...i could use keyboard with kde-konsole, but at the time i'm not able
to install some of kde package.pfffui.I think i'm gonna try to
re-install xserver-xfree86 in is etch versionor got used to this
kbd..and wait

ciao

vale




-
This mail sent through IMP: http://horde.org/imp/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Acer Turion laptops

[Michelasso]

On 8/19/05, Frank <[EMAIL PROTECTED]> wrote:
> Am Donnerstag, 18. August 2005 20:42 schrieb Frederik Schueler:
> > Yeah, I did something similar, additionally the initscript does a
> >
> > echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> >
> > to make the fan shut up ;-)
> 
> Speaking of this, I have to add a short question: Does the ondemand governor
> mean, that I do not need a userspace tool (like "powernowd") anymore for
> scaling the processor frequency? Sounds like a much cleaner solution to me,
> so if this is the case, I'd like to switch to it.
> 

Yes, but the problem with ondemand is that it cannot distinguish if
your ac adapter is connected or not, and so you cannot modify its
policy as for example having always maximum speed pf the processor
when the ac adapter is connected.
You can also consider using the 'conservative' governor, that is
optimized for a battery powered environment and solves the problem of
the latency in transitions between maximum ad minimum frequency in
amd64 cpu's.

Re: mp3 encoding - lame?

[Dean Hamstead]

are vorbis codecs a solution?

Dean

Corey Hickey wrote:

Darnit, I forgot to send this to the list. Sorry.

Azer Demir wrote:


there is a package called toolame, it is nearly identical to lame, but
it is a different project. in i386 (and maybe in other archs) lame
package is available, but not in amd64, i don't know why. but i used
toolame with grip(you can use it in command-line), it works fine.you
just configure your encoder type like "other", and write encoder
executable like "/usr/bin/toolame" in Config/Encode/Encoder path in tabs.



tooLAME is an MPEG-1 layer 2 encoder; LAME is layer 3. I've never used
tooLAME, though, so perhaps it works about as well.

As far as I know, LAME isn't included in Debian for legal reasons.

---
To the original poster:

Unless you need to make an mp3 for a hardware player or something, you'd
be better off using oggenc.

I just tried the lame package from marillat; it seems to work fine for
me. I fed it the audio from a two-hour movie and about an hour of
/dev/urandom. No problem either for a LAME I just built myself using gcc-4.0

Can you provide a sample source audio file (perhaps cut down to a
reasonable size using dd)? Also give the exact command you're using to
encode. I'll see if I can reproduce your problem on my system.

---
On a related note:

The lame source can be easily compiled into a debian package. Whenever
you see a debian directory in a source tree you can just run:

$ dpkg-buildpackage -rfakeroot -uc -b

If you know you have the build dependencies met you can run instead:

$ fakeroot debian/rules binary

(which is a little easier to type)

If you decide to build yourself a debian package of LAME be sure to run
`make uninstall` in the source tree first. Things can get confusing with
a package installed to /usr and the same program installed to /usr/local.

-Corey




--
WWW: http://dean.bong.com.au  LAN: http://www.bong.com.au
EMAIL: [EMAIL PROTECTED]   or   [EMAIL PROTECTED]
ICQ: 16867613


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: illegal user logon

[Corey Hickey]

Dr Gavin Seddon wrote:
> Hi,
> I have noticed in my log there has been people trying to logon to my
> debian box.  Is there any software available to stop this, or should I
> use pam to restrict access?
> Thanks.

There have been a large number of concerted brute-force ssh attacks in
recent months. Don't feel singled out.

enigma:~# grep Illegal /var/log/auth.log | wc -l
2528

That's for the last six days. These are coming from several different IPs.

enigma:~# awk '/Illegal/ {print $10}' /var/log/auth.log | sort -u | wc -l
17

Aside from other solutions, good password choosing is a must. I know a
guy who got his box broken into this way because (1) he was running an
ancient kernel with a local root exploit and (2) one of his local users
had the same username and password.

-Corey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mp3 encoding - lame?

[Corey Hickey]

Darnit, I forgot to send this to the list. Sorry.

Azer Demir wrote:
> there is a package called toolame, it is nearly identical to lame, but
> it is a different project. in i386 (and maybe in other archs) lame
> package is available, but not in amd64, i don't know why. but i used
> toolame with grip(you can use it in command-line), it works fine.you
> just configure your encoder type like "other", and write encoder
> executable like "/usr/bin/toolame" in Config/Encode/Encoder path in tabs.

tooLAME is an MPEG-1 layer 2 encoder; LAME is layer 3. I've never used
tooLAME, though, so perhaps it works about as well.

As far as I know, LAME isn't included in Debian for legal reasons.

---
To the original poster:

Unless you need to make an mp3 for a hardware player or something, you'd
be better off using oggenc.

I just tried the lame package from marillat; it seems to work fine for
me. I fed it the audio from a two-hour movie and about an hour of
/dev/urandom. No problem either for a LAME I just built myself using gcc-4.0

Can you provide a sample source audio file (perhaps cut down to a
reasonable size using dd)? Also give the exact command you're using to
encode. I'll see if I can reproduce your problem on my system.

---
On a related note:

The lame source can be easily compiled into a debian package. Whenever
you see a debian directory in a source tree you can just run:

$ dpkg-buildpackage -rfakeroot -uc -b

If you know you have the build dependencies met you can run instead:

$ fakeroot debian/rules binary

(which is a little easier to type)

If you decide to build yourself a debian package of LAME be sure to run
`make uninstall` in the source tree first. Things can get confusing with
a package installed to /usr and the same program installed to /usr/local.

-Corey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]