Re: dvd+rw-tools and dvdrecord problem / solution
On 9/17/05, Jean-Luc Coulon (f5ibh) <[EMAIL PROTECTED]> wrote: > Le 17.09.2005 04:04:00, Will Dyson a écrit: > Q. What are the dvd+rw-tools for? > A. As implied/already mentionned - to master the DVD media, both +RW/R > and -R[W]. . > > And in the package description: > Description: DVD+-RW/R tools > This package includes a format utility for DVD+-RW media, a frontend > to mkisofs for burning DVD+-RW/R and some associated tools. > > I'm a bit puzzled... After looking at the dvd+rw-format source code (http://fy.chalmers.se/~appro/linux/DVD+RW/tools/dvd+rw-format.cpp), it seems that I was wrong about dvd+rw-format not being useful at all for the -RW disc variety. It can perform blanking of DVD-RW (and DVD-RAM) media. -- Will Dyson
Re: dvd+rw-tools and dvdrecord problem / solution
On 9/16/05, ael <[EMAIL PROTECTED]> wrote: > Lennart Sorensen wrote: > > On Thu, Sep 15, 2005 at 10:55:56PM -0400, Will Dyson wrote: > > > >>I think your use of DVD-RWs is the problem. The dvd+rw-format tool is > >>only useful for +RW discs. As you've discovered, a -RW DVD disc is > >>more like a high-capacity CDRW. > > The original version indeed only supported +rw, but -rw has been fully > supported for a long time now. But I admit that I have used it only on > i386 architecture. Right. The growisofs program fully supports burning to -rw. However, the -rw format does not require the same format operation that a +rw does. Therefor, the dvd+rw-format tool is not useful with -rw discs. -- Will Dyson
Re: dvd+rw-tools and dvdrecord problem / solution
On 9/14/05, Bill Brown <[EMAIL PROTECTED]> wrote: > > I've been tinkering with the dvdrecord and dvd+rw-tools packages trying to > get a good dvd burn backup process going, and I found what appears to be a > bug in the dvd+rw-format tool. > > Problem: > > Issuing a "dvd+rw-format " is supposed to start > formatting and then after a minute or so, move the format process to the > background, and then format on the fly as you add data. >From the page > http://fy.chalmers.se/~appro/linux/DVD+RW/ > However, using the dvd+rw-format on my Memorex DVD-RWs, it starts I think your use of DVD-RWs is the problem. The dvd+rw-format tool is only useful for +RW discs. As you've discovered, a -RW DVD disc is more like a high-capacity CDRW. -- Will Dyson
Re: libswt-gtk-3.1-java unmet dependencies
On 9/2/05, Max <[EMAIL PROTECTED]> wrote: > What's going on with libswt-gtk-3.1-java package? > It's being "kept back" for quite a while because of unmet dependencies: > >libswt-gtk-3.1-java: Depends: libswt-gtk-3.1-jni (= 3.0+3.1M4-4) but > 3.0+3.1M4-3 is to be installed > > I worry about that since it seems to be a reason for Bug # 322897 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322897 > Does anybody see this bug under debian-amd64/unstable ? I've noticed this as well. It looks like this is the reason for it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324030 Note that while swt-gtk 3.1 was uploaded on Sept 9, it is still FTBFS on alpha and ia64, so amd64 is probably still out of luck... -- Will Dyson
Re: sid x.org broken?
On 8/3/05, Miguel Guzman Miranda <[EMAIL PROTECTED]> wrote: > Hi there, > > I just installed a new debian amd64 system and wanted to have directly > an x.org based system instead of installing xfree and then switching. > > It seems x.org is not in etch, and in sid x.org is broken, when > installing xserver-xorg it gives: > > expr: non-numeric argument > > Is this going to be fixed or is it better for the time being to keep > xfree86? It is much more likely to be fixed if you make a detailed bug report to the BTS. -- Will Dyson
Re: dvd::rip doesn't find tools
On 5/18/05, antongiulio <[EMAIL PROTECTED]> wrote: > Hi, > > I have installed dvd:rip and needed tools, but when I launch it, dvd::rip > shows a window with list of "failed" dipendencies. In "preferences" windows > instead, I got all "OKs". Versions of tools seem ok. Is it a bug of package > or my error on configuration? When you run the problematic version of dvd::rip from a terminal, you'll notice that it prints a warning about not being able to load libdl.so. It seems that this is caused by whatever nasty hackery dvd::rip does to work around some supposed NPTL bugs in transcode. Go to the Misc Options tab of dvd::rip's preferences and turn that sillyness off. -- Will Dyson
Re: dri from chroot
On Fri, 25 Feb 2005 09:47:07 +0100, Filippo Carone <[EMAIL PROTECTED]> wrote: > Hi everybody, > I installed the chroot to run 32bit apps, but I'm not able to access > the /dev/dri/card0 file either binding /dev on /chroot/dev or creating > /chroot/dev/dri/card0 . stracing on glxinfo inside the chroot or by > dchroot: Unfortunatly, the DRI was not designed with 64/32-bit compatibility in mind. Currently, a 32-bit process cannot use the DRI under a 64-bit kernel. A proper 64/32 compatibility layer is proving hard to make without losing backwards compatibility. -- Will Dyson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: switch back from gcc-3.4 to pure64
On Fri, 28 Jan 2005 15:23:30 +, Andrei Mikhailovsky <[EMAIL PROTECTED]> wrote: > I've followed the steps to move from gcc4 to pure64 and found out that > after the migration, some of the packages haven't been updated. Quite a > lot actually, about 100 or so packages still had .gcc4 in their version > numbers. Here is the list of them: > Does anyone know of the quick way of reinstalling them? I've tried doing > apt-get --reinstall install , but apt failed with: > > Reinstallation of is not possible, it cannot be > downloaded. Apt does consider it a downgrade, so you must pin the priority for the package above 1000 using the /etc/apt/preferences file. See the apt_preferences manpage. I did this last night and ended up having to use --force-yes on apt-get. I made a backup and crossed my fingers, but it seemed to work. -- Will Dyson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Flash (libflash) Packages
On Sun, 09 Jan 2005 14:41:30 +0100, Rafael Steiner <[EMAIL PROTECTED]> wrote: > The original Debian Packages do not work with amd64, so I built my own > with the Patch from the sourcefoge Forums. > > It works good for me, so if you want Flash without an chroot, try it > out :) You might consider submitting a BTS report on this issue. Based on my reading of the patch, it is probably (still) broken on other 64-bit arches as well, depending on how wide their ints and longs are. I'll try out your packages later, however. -- Will Dyson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why gcc-3.4 and pure64 not synchrone ?
On Sat, 01 Jan 2005 10:36:45 +0100, Harald Dunkel <[EMAIL PROTECTED]> wrote: > AFAIK there is _no_ automatic cron job looking for new source > packages, rebuilding the *.deb, and then running an upload to > Alioth. > > The gcc-3.4 packages are built manually by volunteers. > Probably they were busy IRL during the holidays. I see. Do you know if there is a technical issue blocking the use of the standard debian build scripts? -- Will Dyson - Consultant http://www.lucidts.com/
Re: recent update causes postfix hang
On Sat, 1 Jan 2005 17:49:04 +0100, Sander <[EMAIL PROTECTED]> wrote: > And this as a sort-of solution: > http://lists.debian.org/debian-amd64/2004/12/msg00569.html > > I didn't try to downgrade, but think that might work. Rebuilding the debian source package seems to have fixed it here. -- Will Dyson - Consultant http://www.lucidts.com/
Re: Why gcc-3.4 and pure64 not synchrone ?
On Fri, 31 Dec 2004 16:09:22 +, Ludovic watteaux <[EMAIL PROTECTED]> wrote: > Hi evrybody, > > I want to know why the pakages in gcc-3.4 are generaly olders versions that > the pure64 repository ? I'd guess that some of the problem is applying the gcc4 patches that many source packages need. If the patch does not apply cleanly to a new version of the source (or if the previous version did not need a patch), manual intervention is needed. However, this cannot be the only explanation. One of the notable out of date packages is libxine1 (at 1-rc7-1 in the gcc-3.4 archive). I just downloaded and built the source (using apt-src) for the current version (1.0-1), and no manual intervention of any kind was required. Given the speed at which my relativly inexpensive athlon64 3000+ cranks through compiles, I doubt that lack of build daemon resources is the problem either. I would be very interested in knowing how the gcc-3.4 archive is built, what the real problem is, and if there is any way I can help out. -- Will Dyson
Re: recent update causes postfix hang
On Fri, 31 Dec 2004 13:04:34 -0800, Tupshin Harper <[EMAIL PROTECTED]> wrote: > I updated my gcc-3.4 amd64 system today, which (among other things) > included an update to libc6: 2.3.2.ds1-20.0.0.1.gcc4. > > After doing so, postfix hangs when receiving an SMTP connection. > Eventually the sender times out. Any ideas? Anybody else having such a > problem? I'm seeing it too. -- Will Dyson - Consultant http://www.lucidts.com/
Re: Kernel panic on MSI K8T
On Mon, 27 Dec 2004 21:56:12 +0200, Kyuu Eturautti <[EMAIL PROTECTED]> wrote: > Actually, from what I'm reading... > K8T Neo series - Via > K8N Neo series - nVidia /me looks at the box my mobo came in Ah, I see that is correct. Thanks for clearing that up. > Neo is just something MSI has been using for a while to make their > product names "interesting" and "futuristic" and . > > In any case, I'll be testing 2.6.10 and I'll see what happens. It's very > likely I just have a faulty mb as well. Do you always get that "Kernel BUG at r8169.c:713" and similar stack trace? I'd be surprised if a faulty component resulted in a reproducable error. -- Will Dyson - Consultant http://www.lucidts.com/
Re: Kernel panic on MSI K8T
On Mon, 27 Dec 2004 11:46:41 +0100, Pere Castañer Sardà <[EMAIL PROTECTED]> wrote: > > I disagree. I own a MSI K8T Neo with a 64bit AMD chip and all is going sweet > and smooth in my debian amd64 linux workstation. I use 2.6.9 and gcc3.4 > repository. Perhaps your motherboards have hardware problems not realted in > the design like bad motherboard assembly. As mentioned previously, I've had a positive experience with my K8T Neo2 as well (ok, the onboard audio is terrible, but that is hardly a surprise). The key difference is that the MSI K8T Neo boards are Nforce3-based, while the non-Neo K8T is VIA-based. Bad, confusing product naming.
Re: Kernel panic on MSI K8T
On Mon, 27 Dec 2004 07:31:13 +0200, Kyuu Eturautti <[EMAIL PROTECTED]> wrote: > Problem is this - when I upload a larger amount of data onto it, the > whole thing crashes. I can copy a few megabytes or even larger amounts > when the speed is low (ADSL), but when I start transferring hundreds of > megs through the LAN, it always crashes within minutes - or sometimes > seconds. > > As I had several USB "issues" with the system (as discussed here a few > months ago), I tried using only PS/2 devices as well, but it didn't have > any effect in the end. Seems like an r8169 issue, but I'll let someone > else make a better guess. I took a picture of the kernel panic message: > http://vekotin.org/shared/yue_panic.jpg That sure looks like a problem with the r8169 driver to me. Try the recently released 2.6.10 kernel. If you still experience the problem with that kernel, I'd try bringing the issue up on the kernel mailing list or the net-dev mailing list. For what it's worth, I have an r8169 on my MSI K8N-Neo2. I haven't seen this problem, but I only use it as my internet connection. -- Will Dyson - Consultant http://www.lucidts.com/
