Re: ATI Drivers

[luk]

John Baab wrote:
> I am attempting to install the ati drives located here:
> http://rufus.hackish.org/~rufus/files/fglrx/
> 
> Using the instructions in this faq:
> http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html
> 
> /usr/src/modules/fglrx-kernel-src/agpgart_be.c: In function `__fgl_agp_init':
>

check this site and apply patch:

http://ati.cchtml.com/show_bug.cgi?id=110

Lukasz Pieczara


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

Re: Installer and installed system differ in disk enumeration

[Toshikazu Aiyama, Ph.D.]

A.E.Lawrence wrote:

> The problems arise before those options are available :-( But it is
> possible to use grub's editing options to get an initial system. Then
> one can edit the grub configuration and /etc/fstab to match whichever
> kernel is loaded. The point is that the installer is setting these
> things up incorrectly. Short of using something like disc labels or
> somehow ensuring that all kernels agree on enumeration in all
> circumstances, there doesn't seem to be an easy solution.

I do not want to engage in any argument here. And I do not want to justify why
I can install the system, and why you cannot, or at least you have some great
difficulty.

I have a similar set up with you:
ASUS a8n-sli Deluxe mbrd populated with 5 hard disks:

a) 1 scsi MO on adaptec 2940UW
b) 1 PATA primary master 
c) 4 sata on nv_sata, none on sil_SATA

In addition, I have 1 DVD-RAM, and 1 CD-RW on PATA secondary.

I do not use grub becasue it uses a kind of relative disk assignment: 1st disk
is hdd0, and 2nd disk is hdd1, and so on; thus if I change the disk
configurations, there is no easy way to boot the system, at least, to
grub-ignorant people like me.   And since you can edit grub setting, you should
be able to install lilo instead.

If you are using an installer, the steps are as follows, I think.  After a
chosen kernel is installed, we can choose a boot loader: grub or lilo.  I
believe grub or lilo is a mutually exclusive options; thus since you are
talking about grub, you are in the position to follow my suggestions.  Of
course, you can simply ignore me.

If I use non-default pre-compiled image, disk on 2940UW is recognized as scsi4
by the installer kernel, and the same disk is recognized as scsi0 by the
installed kernel.  But if I use non-default image, the SATA2 disk on nv_sata is
recognized as scsi0 by both installer kerenel and the installed kernel.

Toshikazu Aiyama



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/


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

ATI Drivers

[John Baab]

I am attempting to install the ati drives located here:
http://rufus.hackish.org/~rufus/files/fglrx/

Using the instructions in this faq:
http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html

Which seems to be the recomendation around here.

Now I am running into problems in step:
4. Install packages and compile the kernel module
Here is the output:

optimusprime:/usr/src/kernel-source-2.6.11# fakeroot make-kpkg
--append-to-version "-amd64-k8" --added-modules fglrx-kernel-src
modules_image
for module in /usr/src/modules/fglrx-kernel-src ; do   \
  if test -d  $module; then\
(cd $module;  \
  if ./debian/rules KVERS="2.6.11-amd64-k8"
KSRC="/usr/src/kernel-so urce-2.6.11" \
 KMAINT="Unknown Kernel Package
Maintainer" KEMAIL=" [EMAIL PROTECTED]" 
\

KPKG_DEST_DIR="/usr/src/kernel-source-2.6.11/.." \
 KPKG_MAINTAINER="Unknown Kernel Package
Maintainer" \
 KPKG_EXTRAV_ARG="EXTRAVERSION=-amd64-k8"\
 ARCH="x86_64"  \
 KDREV="2.6.11-9" kdist_image; then\
  echo "Module $module processed fine";\
  else  \
   echo "Module $module failed.";  \
   if [ "X" != "X" ]; then  \
  echo "Perhaps $module does not understand --rootcmd?";  \
  echo "If you see messages that indicate that it is not"; \
  echo "in fact being built as root, please file a bug ";  \
  echo "against $module."; \
   fi;  \
   echo "Hit return to Continue";   \
 read ans;\
  fi;   \
 );\
  fi;  \
done
make[1]: Entering directory `/usr/src/modules/fglrx-kernel-src'
dh_testdir
/usr/bin/make -C /usr/src/kernel-source-2.6.11
SUBDIRS=/usr/src/modules/fglrx-ke rnel-src modules
make[2]: Entering directory `/usr/src/kernel-source-2.6.11'
  CC [M]  /usr/src/modules/fglrx-kernel-src/agp3.o
  CC [M]  /usr/src/modules/fglrx-kernel-src/nvidia-agp.o
  CC [M]  /usr/src/modules/fglrx-kernel-src/agpgart_be.o
/usr/src/modules/fglrx-kernel-src/agpgart_be.c: In function `__fgl_agp_init':
/usr/src/modules/fglrx-kernel-src/agpgart_be.c:7611: warning:
`pm_register' is d eprecated (declared at include/linux/pm.h:106)
/usr/src/modules/fglrx-kernel-src/agpgart_be.c: In function `__fgl_agp_cleanup':
/usr/src/modules/fglrx-kernel-src/agpgart_be.c:7621: warning:
`pm_unregister_all ' is deprecated (declared at
include/linux/pm.h:116)
  CC [M]  /usr/src/modules/fglrx-kernel-src/i7505-agp.o
  CC [M]  /usr/src/modules/fglrx-kernel-src/firegl_public.o
/usr/src/modules/fglrx-kernel-src/firegl_public.c: In function
`firegl_stub_putm inor':
/usr/src/modules/fglrx-kernel-src/firegl_public.c:509: warning:
`inter_module_pu t' is deprecated (declared at
include/linux/module.h:578)
/usr/src/modules/fglrx-kernel-src/firegl_public.c:511: warning:
`inter_module_un register' is deprecated (declared at
include/linux/module.h:574)
/usr/src/modules/fglrx-kernel-src/firegl_public.c: In function
`firegl_stub_regi ster':
/usr/src/modules/fglrx-kernel-src/firegl_public.c:531: warning:
`inter_module_re gister' is deprecated (declared at
include/linux/module.h:573)
/usr/src/modules/fglrx-kernel-src/firegl_public.c:562: warning:
`inter_module_pu t' is deprecated (declared at
include/linux/module.h:578)
/usr/src/modules/fglrx-kernel-src/firegl_public.c: In function
`firegl_get_user_ ptr':
/usr/src/modules/fglrx-kernel-src/firegl_public.c:1078: warning:
assignment make s pointer from integer without a cast
/usr/src/modules/fglrx-kernel-src/firegl_public.c: In function
`firegl_put_user_ ptr':
/usr/src/modules/fglrx-kernel-src/firegl_public.c:1110: warning: cast
from point er to integer of different size
/usr/src/modules/fglrx-kernel-src/firegl_public.c:1110: warning: cast
from point er to integer of different size
/usr/src/modules/fglrx-kernel-src/firegl_public.c:1110: warning: cast
from point er to integer of different size
/usr/src/modules/fglrx-kernel-src/firegl_public.c:1110: warning: cast
from point er to integer of different size
/usr/src/modules/fglrx-kernel-src/firegl_public.c: In function
`__ke_get_vm_phys _addr':
/usr/src/modules/fglrx-kernel-src/firegl_public.c:1673: error:
structure has no member named `pud'
/usr/src/modules/fglrx-kernel-src/firegl_public.c: In function
`do_vm_shm_nopage ':
/usr/src/modules/fglrx

Re: amd64 porters IRC meeting: preparations for sarge

[Alex Perry]

Frederik Schueler wrote:
Now, what we need to start the meeting is: [...]
18:00 UTC is fine by me.  Don't forget we've switched to summer time; 
it's 11am PDT for example.  I'd like to avoid 8:00 UTC because that's 
1am PDT but 7:00 UTC would be usable for me.

I suspect another relevant agenda item is: Which combinations of 
sarge/testing/sid vs GCC versions ... to continue running buildd's for.

I suggest we segue into an adjacent topic area (once the main topics are 
dealt with):  Should debian-amd64 actively push multiarch forward (to 
merge i386 and amd64) ? Should we have packages with matching names that 
provide amd64 script wrappers for running chrooted i386 binaries ?

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

openoffice.org-amd64 works great! trash out 32-bit version ;-)

[Max]

Hello!
I've just successfully installed openoffice.org-amd64 and it works just great!
No need to keep 32-bit openoffice in chroot32 anymore.
The installation was a bit tricky, so here what I've done:
1) Add the following line to your /etc/apt/sources.list:
deb http://debian-amd64.alioth.debian.org/openoffice.org/ ./
2) manually download openoffice.org-debian-files_1.1.2-2+1.0.1_all.deb from
http://debian-amd64.alioth.debian.org/openoffice.org/openoffice.org-debian-files_1.1.2-2+1.0.1_all.deb
3) Force the installation of openoffice.org-debian-files:
dpkg -i --force-all openoffice.org-debian-files_1.1.2-2+1.0.1_all.deb
4) Install openoffice.org-amd64 with the following command:
apt-get install openoffice.org-amd64 openoffice.org openoffice.org-l10n-en 
ttf-opensymbol
5) (Optionally) install any other openoffice.org hyphenation/spellcheck/etc. 
files via apt-get (as usual).
Enjoy OpenOffice ;-)
Max
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Random freezing...

[tony mancill]

Lennart Sorensen wrote:
> On Sat, Apr 09, 2005 at 09:59:51PM -0700, tony mancill wrote:
> 
>>I was recently experiencing some random freezes, but can't attribute it to
>>software.  I added some additional hard drives and changed my overclocking
>>slightly (unfortunately at the same time - poor decision on my part), and
>>for a couple days couldn't go more than a couple hours without the system
>>locking up.  I assumed that the problem might be related to
>>inadequate/unsable power from the power-supply.  Reverting to the standard
>>CPU voltages and merely overclocking the FSB by 10% cleared everything up.
>>
>>So FWIW, I'm running a 3500+ on an Asus AV8-Deluxe mobo in an Antec Sonata
>>case (350W PS); pure64 w/stock 2.6.11 kernel and nvidia 5200.
> 
> 
> I don't think I would run too many drives on a system with only a 350W
> power supply.  Do lmsensors work on that board?  maybe you could see
> what the voltages are running at. :)
> 
> Len Sorensen

Yeah, I'm going to pull one of the drives out here in a couple days.  I'm
not sure how much I can trust the output of lmsensors.  Obviously the CPU
fan is running.  The temps look about right, at least...

Cheers,
tony

[EMAIL PROTECTED]:~$ sensors
w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.48 V  (min =  +0.92 V, max =  +1.02 V)
+12V: +11.49 V  (min = +10.82 V, max = +13.19 V)
+3.3V: +3.31 V  (min =  +3.14 V, max =  +3.47 V)
+5V:   +4.99 V  (min =  +4.75 V, max =  +5.25 V)
-12V: -14.91 V  (min = -10.80 V, max = -13.18 V)
V5SB:  +5.11 V  (min =  +4.76 V, max =  +5.24 V)
VBat:  +0.93 V  (min =  +2.40 V, max =  +3.60 V)
fan1:0 RPM  (min = 5113 RPM, div = 2)
CPU Fan: 0 RPM  (min = 16463 RPM, div = 2)
fan3: 1188 RPM  (min = 16875 RPM, div = 8)
M/B Temp:+25ÂC  (high =+1ÂC, hyst =+4ÂC)   sensor = thermistor

CPU Temp:  +38.0ÂC  (high =   +80ÂC, hyst =   +75ÂC)   sensor = thermistor

temp3: +21.0ÂC  (high =   +80ÂC, hyst =   +75ÂC)   sensor = thermistor

vid:  +0.975 V  (VRM Version 9.0)


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

Re: broken ssl in evolution-2.2

[Kurt Roeckx]

On Fri, Apr 08, 2005 at 01:36:06PM +0100, Andrei Mikhailovsky wrote:
> Hello.
> 
> after upgrading to evolution-2.2 my imaps mailboxes stoped working with
> error: SSL unsupported. I've checked the sources and in debian/rules
> there is --without-ssl option. I've tried compiling without this option,
> the ssl unsupported is still there.

This has been filed as a grave bug against the package:
http://bugs.debian.org/304243



Kurt


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

Re: broken ssl in evolution-2.2

[daniel_e]

Same problem here :(
$ ldd `which evolution` | grep -iE "(ssl|tls)"
libgnutls.so.11 => /usr/lib/libgnutls.so.11 (0x002a97ee)

I also get this one if I try to send mail:
/usr/bin/evolution: relocation error:
/usr/lib/evolution/2.2/components/libevolution-mail.so: undefined symbol:
camel_smime_context_new

Program exited with code 0177.

$ ldd /usr/lib/evolution/2.2/components/libevolution-mail.so | grep -i camel
libcamel-1.2.so.0 => /usr/lib/libcamel-1.2.so.0 (0x002a96563000)
libcamel-provider-1.2.so.3 => /usr/lib/libcamel-provider-1.2.so.3
(0x002a966b8000)

$ dpkg -l libcamel1.2-0 evolution | grep ^ii ii  libcamel1.2-0  1.2.1-1
The Evolution MIME message handling library
ii  evolution  2.2.1.1-1  The groupware suite

Quoting Andrei Mikhailovsky <[EMAIL PROTECTED]>:

> Hello.
>
> after upgrading to evolution-2.2 my imaps mailboxes stoped working with
> error: SSL unsupported. I've checked the sources and in debian/rules
> there is --without-ssl option. I've tried compiling without this option,
> the ssl unsupported is still there.
>
> in my chroot, ssl works fine.
>
> After doing ldd on evolution i get the following:
>
> chroot:
> $ which evolution-2.2 |xargs ldd |grep ssl |wc -l
> 1
> $ which evolution-2.2 |xargs ldd |grep tls |wc -l
> 8
>
>
> non-chroot:
> $ which evolution-2.2 |xargs ldd |grep ssl |wc -l
> 0
> $ which evolution-2.2 |xargs ldd |grep tls |wc -l
> 1
>
> Is there a particular reason for disabling ssl support?
>
> Many thanks,
>
> --
> Andrei
>




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

amd64 porters IRC meeting: preparations for sarge

[Frederik Schueler]

Fellow debian-amd64 porters,


I would like to collect additional topics and scedule proposals for 
the IRC meeting about the future of the debian-amd64 sarge distribution.

What I would like to discuss, is how we are going to handle:

- the sarge release of debian-amd64

- patched versions of packages in sarge

- security updates

- CD and DVD installation media

Additionally, I would like to discuss if we should fork debian-installer
and use it with newer kernel versions than 2.6.8, since an increasing
number of new amd64 mainboards do ship with hardware not supported by
that ancient kernel version (megaraid, sk98lin, sata_nv, sata_sis to 
name a few).


Now, what we need to start the meeting is: 

1. a fixed date next week, or at the weekend? suited for everyone who
   wants to attend, for example April, 19th 18:00 UTC? or better 
   8:00 UTC? 

2. additional items for the agenda.


Kind regards
Frederik Schueler

-- 
ENOSIG


signature.asc
Description: Digital signature

Re: Nvidia problems... again

[James Titcumb]

Hi Sven,
Yes, the method in /usr/share/doc/nvidia-kernel-source/README.Debian 
works fine for a stock debian kernel. However, seeing as I'm trying to 
do this with a slightly modified kernel, I think I need patches for it.

I did try both methods listed, but neither work. It's not really about 
the installation of the driver, as thats fine. Its a problem *after* the 
driver loads

Cheers,
James
And confirming nvidia 7174 with a Debian 2.6.11-9-amd64-k8 standard
kernel (I have just upgraded from 7167 to 7174). Card is Nvidia
GeForce FX 5700 LE. No issues at all. Follow the Debian way as
described in /usr/share/doc/nvidia-kernel-source/README.Debian
 


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

Re: Nvidia problems... again

[mtms]

On 11 Apr 2005, 18:34, Sven Krahn <[EMAIL PROTECTED]> wrote:

> And confirming nvidia 7174 with a Debian 2.6.11-9-amd64-k8 standard
> kernel (I have just upgraded from 7167 to 7174). Card is Nvidia
> GeForce FX 5700 LE. No issues at all. Follow the Debian way as
> described in /usr/share/doc/nvidia-kernel-source/README.Debian

Exactly the same here. Nvidia 7174, debian kernel 2.6.11-9-amd64-k8,
geforce fx 5700 le, mobo is a asus k8v-se deluxe. All works flawlessly.

-- 
 <@,@>  Il corpo del povero cadrebbe subito in pezzi
 [`-']  se non fosse legato ben stretto dal filo dei sogni
 -"-"---Anonimo indiano


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

Re: Nvidia problems... again

[Sven Krahn]

On Apr 11, 2005 4:29 PM, A.E.Lawrence <[EMAIL PROTECTED]> wrote:
> Lennart Sorensen wrote:
> > On Mon, Apr 11, 2005 at 12:16:51AM +0100, A.E.Lawrence wrote:
> >
> >>I have just built  version 7174 of nvidia
> >>(NVIDIA-Linux-x86_64-1.0-7174-pkg2.run) under my freshly minted 2.6.11.7
> >>and the build was fine: just the usual complaint because the library
> >>paths don't quite match. (I haven't tried the video driver yet, but the
> >>kernel module loads happily)
> >
> >
> > Well under the Debian 2.6.11 kernel and using the debian nvidia driver
> > pacakge for 7167 it works percectly (lib paths and all, and no messy 3rd
> > party files in /usr).
> 
> Just to confirm that nvidia 7174 is now also working fine with 2.6.11.7.
> The video card is an asus en6600 which is a GT6600 clone, I believe.
> 

And confirming nvidia 7174 with a Debian 2.6.11-9-amd64-k8 standard
kernel (I have just upgraded from 7167 to 7174). Card is Nvidia
GeForce FX 5700 LE. No issues at all. Follow the Debian way as
described in /usr/share/doc/nvidia-kernel-source/README.Debian

-- 
Best regards / Mit den besten Grüssen
Sven Krahn

Re: Nvidia problems... again

[A.E.Lawrence]

Lennart Sorensen wrote:
On Mon, Apr 11, 2005 at 12:16:51AM +0100, A.E.Lawrence wrote:
I have just built  version 7174 of nvidia
(NVIDIA-Linux-x86_64-1.0-7174-pkg2.run) under my freshly minted 2.6.11.7
and the build was fine: just the usual complaint because the library
paths don't quite match. (I haven't tried the video driver yet, but the
kernel module loads happily)

Well under the Debian 2.6.11 kernel and using the debian nvidia driver
pacakge for 7167 it works percectly (lib paths and all, and no messy 3rd
party files in /usr).
Just to confirm that nvidia 7174 is now also working fine with 2.6.11.7. 
The video card is an asus en6600 which is a GT6600 clone, I believe.

ael

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

Re: Critical mysql bug = remotely changing from PURE64 to 32-bit debian.. possible?

[Pete Harlan]

On Sat, Apr 09, 2005 at 07:29:53AM -0700, Jeremy Gray wrote:
> 
> Is it possible to go from a Sarge Pure64 installation to a 32-bit debian 
> installation remotely?
> 
> (I have KVM over IP access if that helps in the process any.. but no 
> CD-ROM on that server)
> 
> If its possible could someone please tell me the steps to do it or point 
> me to a url that covers it?
> 
> Thanks!
> 
> See below for why I think I need to switch to 32 bit

Without knowing exactly what's causing his problems, I wouldn't worry
about them too much unless you see them on your own setup.  There are
surely plenty of cases where people have run MySQL successfully in
64-bit mode, on similar hardware and software configuration as his,
without problems.

--Pete


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

Re: need advice for correct sources.list because of broken packages

[Alexander Nagel]

Lennart Sorensen schrieb:
On Sat, Apr 09, 2005 at 11:40:53PM +0200, Alexander Nagel wrote:
redkeep:/home/alex# LC_ALL=POSIX apt-get -o 
Debug::pkgProblemResolver=true install libgtk2.0-dev
Reading Package Lists... Done
Building Dependency Tree... Done
Starting
Starting 2
Investigating zlib1g-dev
Package zlib1g-dev has broken dep on zlib1g
 Considering zlib1g 1009 as a solution to zlib1g-dev 4
 Holding Back zlib1g-dev rather than change zlib1g
Investigating libfreetype6-dev
Package libfreetype6-dev has broken dep on zlib1g-dev
 Considering zlib1g-dev 4 as a solution to libfreetype6-dev 3
 Holding Back libfreetype6-dev rather than change zlib1g-dev
Package libfreetype6-dev has broken dep on libz-dev
 Considering zlib1g-dev 4 as a solution to libfreetype6-dev 3
 Holding Back libfreetype6-dev rather than change libz-dev
 Or group keep for libfreetype6-dev
Investigating libfontconfig1-dev
Package libfontconfig1-dev has broken dep on libfreetype6-dev
 Considering libfreetype6-dev 3 as a solution to libfontconfig1-dev 1
 Holding Back libfontconfig1-dev rather than change libfreetype6-dev
Investigating libpango1.0-dev
Package libpango1.0-dev has broken dep on libfreetype6-dev
 Considering libfreetype6-dev 3 as a solution to libpango1.0-dev 1
 Holding Back libpango1.0-dev rather than change libfreetype6-dev
Investigating libxft-dev
Package libxft-dev has broken dep on libfontconfig1-dev
 Considering libfontconfig1-dev 1 as a solution to libxft-dev 0
 Holding Back libxft-dev rather than change libfontconfig1-dev
Investigating libgtk2.0-dev
Package libgtk2.0-dev has broken dep on libpango1.0-dev
 Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
   Reinst Failed early because of zlib1g
   Reinst Failed because of zlib1g-dev
   Reinst Failed because of zlib1g-dev
   Reinst Failed because of libfreetype6-dev
Investigating xlibs-static-dev
Package xlibs-static-dev has broken dep on zlib1g-dev
 Considering zlib1g-dev 4 as a solution to xlibs-static-dev 6
 Holding Back xlibs-static-dev rather than change zlib1g-dev
Package xlibs-static-dev has broken dep on libz-dev
 Considering zlib1g-dev 4 as a solution to xlibs-static-dev 6
 Holding Back xlibs-static-dev rather than change libz-dev
 Or group keep for xlibs-static-dev
Investigating libgtk2.0-dev
Package libgtk2.0-dev has broken dep on libpango1.0-dev
 Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
Investigating libx11-dev
Package libx11-dev has broken dep on xlibs-static-dev
 Considering xlibs-static-dev 6 as a solution to libx11-dev 8
 Holding Back libx11-dev rather than change xlibs-static-dev
Investigating libxi-dev
Package libxi-dev has broken dep on libx11-dev
 Considering libx11-dev 8 as a solution to libxi-dev 6
 Holding Back libxi-dev rather than change libx11-dev
Investigating libxrender-dev
Package libxrender-dev has broken dep on libx11-dev
 Considering libx11-dev 8 as a solution to libxrender-dev 1
 Holding Back libxrender-dev rather than change libx11-dev
Investigating libxv-dev
Package libxv-dev has broken dep on libx11-dev
 Considering libx11-dev 8 as a solution to libxv-dev 0
 Holding Back libxv-dev rather than change libx11-dev
Investigating libgtk2.0-dev
Package libgtk2.0-dev has broken dep on libpango1.0-dev
 Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
Package libgtk2.0-dev has broken dep on libx11-dev
 Considering libx11-dev 8 as a solution to libgtk2.0-dev 
 Re-Instated libxi-dev
 Re-Instated libxv-dev
   Reinst Failed because of zlib1g-dev
   Reinst Failed because of zlib1g-dev
   Reinst Failed because of xlibs-static-dev
Package libgtk2.0-dev has broken dep on xlibs-dev
 Considering xlibs-dev 4 as a solution to libgtk2.0-dev 
 Re-Instated libice-dev
 Re-Instated libsm-dev
   Reinst Failed because of libx11-dev
Investigating libxi-dev
Package libxi-dev has broken dep on libx11-dev
 Considering libx11-dev 8 as a solution to libxi-dev 6
 Holding Back libxi-dev rather than change libx11-dev
Investigating libxv-dev
Package libxv-dev has broken dep on libx11-dev
 Considering libx11-dev 8 as a solution to libxv-dev 0
 Holding Back libxv-dev rather than change libx11-dev
Investigating libgtk2.0-dev
Package libgtk2.0-dev has broken dep on libpango1.0-dev
 Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
Package libgtk2.0-dev has broken dep on libx11-dev
 Considering libx11-dev 8 as a solution to libgtk2.0-dev 
Package libgtk2.0-dev has broken dep on xlibs-dev
 Considering xlibs-dev 4 as a solution to libgtk2.0-dev 
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation

kile crashes

[Dr Gavin Seddon]

Hi,
When I run the wizard on Kile I get told Kile has crashed probably due
to an application error, it has received the 'SIGSEGV' signal. Has
anyone dealt with this?
Gavin.


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

Re: Nvidia problems... again

[Lennart Sorensen]

On Mon, Apr 11, 2005 at 12:16:51AM +0100, A.E.Lawrence wrote:
> I have just built  version 7174 of nvidia
> (NVIDIA-Linux-x86_64-1.0-7174-pkg2.run) under my freshly minted 2.6.11.7
> and the build was fine: just the usual complaint because the library
> paths don't quite match. (I haven't tried the video driver yet, but the
> kernel module loads happily)

Well under the Debian 2.6.11 kernel and using the debian nvidia driver
pacakge for 7167 it works percectly (lib paths and all, and no messy 3rd
party files in /usr).

I guess using just "The Debian Way" works fine.

Len Sorensen


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

Re: Re: ASUS A8V-E Deluxe working

[Lennart Sorensen]

On Sat, Apr 09, 2005 at 07:19:27AM -0700, James McEwan wrote:
> I have an ASUS K8V SE DELUXE...gave up the ide drives and boot from
> the SATA drives on the VIA chip VT8237. The 120 G Seagate Baracuda's are
> striped. I tryed installing WIN XP 64 bit just to see if i'd work but the
> the drivers on the mobo disk (i put 'em on floppy) are'nt compatible, so I
> assume the same will hold true for Debians installer, Although I did have
> Free BSD on the Promise raid controller with same drives and 2 other IDE
> drives and the BIOS set to the raid configurement, BSD "saw" everything
> Windows  couldn't, but that was many reformats ago. Will Debian "see"
> the SATA drives  or do I gotta install to an IDE drive and then install
> the drivers for the SATA"s? Now I read of the onboard Marvel Gigalan
> miniport adapter not workin with Debian.any suggestions.I can't
> do much without a GUI and this stuff sounds complicated!  James.

Well as far as I can tell that board is very similar to the A8V Deluxe
(just different socket mainly).

So far I have no problems with the SATA controller in the VIA.  I do not
have the garbage proprietary software raid enabled, I use linux MD
software raid instead.  The promise 20378 controller I don't have
working yet (ft3xx drivers appear to be binary only so far).

The onboard gigabit works perfectly with the sk98lin driver on the A8V,
but perhaps yours uses PCI-e instead which I have herad causes some
problems.  The A8V does not have internal devices as PCI-e so it works
just fine.

Whatever you do, forget the board has onboard "raid" if you want life
simple.  Proprietary software raid has very little purpose unless you
run windows (which doesn't by default support software raid, so having
drivers do it is handy).

Len Sorensen


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

Re: Random freezing...

[Lennart Sorensen]

On Sat, Apr 09, 2005 at 09:59:51PM -0700, tony mancill wrote:
> I was recently experiencing some random freezes, but can't attribute it to
> software.  I added some additional hard drives and changed my overclocking
> slightly (unfortunately at the same time - poor decision on my part), and
> for a couple days couldn't go more than a couple hours without the system
> locking up.  I assumed that the problem might be related to
> inadequate/unsable power from the power-supply.  Reverting to the standard
> CPU voltages and merely overclocking the FSB by 10% cleared everything up.
> 
> So FWIW, I'm running a 3500+ on an Asus AV8-Deluxe mobo in an Antec Sonata
> case (350W PS); pure64 w/stock 2.6.11 kernel and nvidia 5200.

I don't think I would run too many drives on a system with only a 350W
power supply.  Do lmsensors work on that board?  maybe you could see
what the voltages are running at. :)

Len Sorensen


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

Re: Random freezing...

[Lennart Sorensen]

On Sat, Apr 09, 2005 at 07:42:39PM +0100, James Titcumb wrote:
> If and when I get my nvidia module working properly, I'll report back if 
> I get any more crashes ;)

Easy to do if you just use apt-cache search nvidia, and install the
source for the driver and compile the module (module-assistant might
help, but then again sometimes it doesn't).  The installer from nvidia
assumes the wrong paths and is not recomended.

Len Sorensen


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

Re: need advice for correct sources.list because of broken packages

[Lennart Sorensen]

On Sat, Apr 09, 2005 at 11:40:53PM +0200, Alexander Nagel wrote:
> redkeep:/home/alex# LC_ALL=POSIX apt-get -o 
> Debug::pkgProblemResolver=true install libgtk2.0-dev
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Starting
> Starting 2
> Investigating zlib1g-dev
> Package zlib1g-dev has broken dep on zlib1g
>   Considering zlib1g 1009 as a solution to zlib1g-dev 4
>   Holding Back zlib1g-dev rather than change zlib1g
> Investigating libfreetype6-dev
> Package libfreetype6-dev has broken dep on zlib1g-dev
>   Considering zlib1g-dev 4 as a solution to libfreetype6-dev 3
>   Holding Back libfreetype6-dev rather than change zlib1g-dev
> Package libfreetype6-dev has broken dep on libz-dev
>   Considering zlib1g-dev 4 as a solution to libfreetype6-dev 3
>   Holding Back libfreetype6-dev rather than change libz-dev
>   Or group keep for libfreetype6-dev
> Investigating libfontconfig1-dev
> Package libfontconfig1-dev has broken dep on libfreetype6-dev
>   Considering libfreetype6-dev 3 as a solution to libfontconfig1-dev 1
>   Holding Back libfontconfig1-dev rather than change libfreetype6-dev
> Investigating libpango1.0-dev
> Package libpango1.0-dev has broken dep on libfreetype6-dev
>   Considering libfreetype6-dev 3 as a solution to libpango1.0-dev 1
>   Holding Back libpango1.0-dev rather than change libfreetype6-dev
> Investigating libxft-dev
> Package libxft-dev has broken dep on libfontconfig1-dev
>   Considering libfontconfig1-dev 1 as a solution to libxft-dev 0
>   Holding Back libxft-dev rather than change libfontconfig1-dev
> Investigating libgtk2.0-dev
> Package libgtk2.0-dev has broken dep on libpango1.0-dev
>   Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
> Reinst Failed early because of zlib1g
> Reinst Failed because of zlib1g-dev
> Reinst Failed because of zlib1g-dev
> Reinst Failed because of libfreetype6-dev
> Investigating xlibs-static-dev
> Package xlibs-static-dev has broken dep on zlib1g-dev
>   Considering zlib1g-dev 4 as a solution to xlibs-static-dev 6
>   Holding Back xlibs-static-dev rather than change zlib1g-dev
> Package xlibs-static-dev has broken dep on libz-dev
>   Considering zlib1g-dev 4 as a solution to xlibs-static-dev 6
>   Holding Back xlibs-static-dev rather than change libz-dev
>   Or group keep for xlibs-static-dev
> Investigating libgtk2.0-dev
> Package libgtk2.0-dev has broken dep on libpango1.0-dev
>   Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
> Investigating libx11-dev
> Package libx11-dev has broken dep on xlibs-static-dev
>   Considering xlibs-static-dev 6 as a solution to libx11-dev 8
>   Holding Back libx11-dev rather than change xlibs-static-dev
> Investigating libxi-dev
> Package libxi-dev has broken dep on libx11-dev
>   Considering libx11-dev 8 as a solution to libxi-dev 6
>   Holding Back libxi-dev rather than change libx11-dev
> Investigating libxrender-dev
> Package libxrender-dev has broken dep on libx11-dev
>   Considering libx11-dev 8 as a solution to libxrender-dev 1
>   Holding Back libxrender-dev rather than change libx11-dev
> Investigating libxv-dev
> Package libxv-dev has broken dep on libx11-dev
>   Considering libx11-dev 8 as a solution to libxv-dev 0
>   Holding Back libxv-dev rather than change libx11-dev
> Investigating libgtk2.0-dev
> Package libgtk2.0-dev has broken dep on libpango1.0-dev
>   Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
> Package libgtk2.0-dev has broken dep on libx11-dev
>   Considering libx11-dev 8 as a solution to libgtk2.0-dev 
>   Re-Instated libxi-dev
>   Re-Instated libxv-dev
> Reinst Failed because of zlib1g-dev
> Reinst Failed because of zlib1g-dev
> Reinst Failed because of xlibs-static-dev
> Package libgtk2.0-dev has broken dep on xlibs-dev
>   Considering xlibs-dev 4 as a solution to libgtk2.0-dev 
>   Re-Instated libice-dev
>   Re-Instated libsm-dev
> Reinst Failed because of libx11-dev
> Investigating libxi-dev
> Package libxi-dev has broken dep on libx11-dev
>   Considering libx11-dev 8 as a solution to libxi-dev 6
>   Holding Back libxi-dev rather than change libx11-dev
> Investigating libxv-dev
> Package libxv-dev has broken dep on libx11-dev
>   Considering libx11-dev 8 as a solution to libxv-dev 0
>   Holding Back libxv-dev rather than change libx11-dev
> Investigating libgtk2.0-dev
> Package libgtk2.0-dev has broken dep on libpango1.0-dev
>   Considering libpango1.0-dev 1 as a solution to libgtk2.0-dev 
> Package libgtk2.0-dev has broken dep on libx11-dev
>   Considering libx11-dev 8 as a solution to libgtk2.0-dev 
> Package libgtk2.0-dev has broken dep on xlibs-dev
>   Considering xlibs-dev 4 as a solution to libgtk2.0-dev 
> Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> 

Re: Is sid ok??

[Alexander Nagel]

Thanks for your answers
i give it a try
Alex
Alexander Nagel schrieb:
Hi list,
i have a strange dependency problem with my fresh install in sarge but 
in sid everything seems to be fine. It is ok to switch to sid? It is 
stable enough to run GNOME with Firefox, Thunderbird, Abiword as main 
applications?
Thanks for your comments
Alex



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

Re: Kernel 2.6.11 and Sarge

[Pete]

Thomas Steffen wrote:
On Apr 11, 2005 12:41 PM, Pete <[EMAIL PROTECTED]> wrote:
 

Hi all,
Is there an easy way to work out when kernel 2.6.11 will hit Sarge at all?
   

On the package page 
 http://packages.debian.org/unstable/devel/kernel-source-2.6.11
you will find a link "developer information" leading to
 http://packages.qa.debian.org/k/kernel-source-2.6.11.html\\
where you find the reason it is not migrating to testing yet.

"Too young, only 1 of 10 days old" means it will take at least another
9 days, but there also seems to be a manual override in place related
to the release or d-i.
I have just downloaded the package from Sid. -2 seems to be ok, -1 had
some nasty issues.
Thomas
 

Thanks Thomas,
So this includes Pure 64 Sarge as well? Not just IA32?
Pete
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel 2.6.11 and Sarge

[Thomas Steffen]

On Apr 11, 2005 12:41 PM, Pete <[EMAIL PROTECTED]> wrote:
> Hi all,
> 
> Is there an easy way to work out when kernel 2.6.11 will hit Sarge at all?

On the package page 
  http://packages.debian.org/unstable/devel/kernel-source-2.6.11
you will find a link "developer information" leading to
  http://packages.qa.debian.org/k/kernel-source-2.6.11.html\\
where you find the reason it is not migrating to testing yet.

"Too young, only 1 of 10 days old" means it will take at least another
9 days, but there also seems to be a manual override in place related
to the release or d-i.

I have just downloaded the package from Sid. -2 seems to be ok, -1 had
some nasty issues.

Thomas




> 
> If someone wants to just tell me when, that's fine, but I'd also like to
> know if there's a way to find out so I don't ask these stupid questions
> in the future  :-)
> 
> Cheers,
> 
> Pete
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
>


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

Kernel 2.6.11 and Sarge

[Pete]

Hi all,
Is there an easy way to work out when kernel 2.6.11 will hit Sarge at all?
If someone wants to just tell me when, that's fine, but I'd also like to 
know if there's a way to find out so I don't ask these stupid questions 
in the future  :-)

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

Re: Firefox and java

[Lorenzo Milesi]

> try to create symbolic lync in /lib/

this worked for ldd, but still not for firefox


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

Re: Nvidia problems... again

[NaiosKAE{FR}]

sorry for responding in a private way,
you can find installers at http://www.lokigames.com/ and 
http://www.lokitorrent.com/

in fact for the unreal tournament family, you'll find linuxinstaller.sh 
on the last CD or on the DVD. it works fine (just run it with root 
privileges and with /bin/sh. don't forget to change owner of ~/.ut200x 
before playing)

have fun...
[EMAIL PROTECTED] a écrit :
Is this in a pure64 environment, or in a 32-bit chroot?
Also, could you send a link to where these binaries are distributed? I might 
have a play around once my graphics drivers work (being presumptious that 
they'll actually work in the end ;) ...)
Cheers,
James
NaiosKAE{FR} <[EMAIL PROTECTED]> wrote :

Hi
I use a differnet way to play
for instance, I have Doom3, Ut2003 & Ut2004, NeverWinterNight, RTCW, 
Medal of honnor, ... running under Debian. I'm using linux binary files 
  to play (loki has most of them). first install the game trough wine 
(not winex) then copy data tree to your game location, copy or install 
teh linux binaries then chown user.grp (by default root.staff with linux 
installers, i moved them to root.games) then chmod 750. finally enjoy 
the game. (that don't work for all the game, for instance warhammer40K 
has no linux binary files at this time)
[...]

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

___
Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net


--
Erwann PENCREACH
Le pénible fardeau de n'avoir rien à faire.
-+- Nicolas Boileau -+-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Is sid ok??

[Clive Menzies]

On (11/04/05 11:11), Alexander Nagel wrote:
> Hi list,
> i have a strange dependency problem with my fresh install in sarge but 
> in sid everything seems to be fine. It is ok to switch to sid? It is 
> stable enough to run GNOME with Firefox, Thunderbird, Abiword as main 
> applications?
> Thanks for your comments
> Alex
Works fine here (I use OOo in the 32 bit chroot rather than abiword) -
Installed in January with KDE and now running Xfce - so far so good;)

Regards

Clive

-- 
www.clivemenzies.co.uk ...
...strategies for business



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

Re: Is sid ok??

[Dr Gavin Seddon]

Hi,
I have had no problems with my apps.  I use Galeon, kde and Abiword runs
fine.  But I must say things don't work with windowmaker.  For text
editing/processing I have started using Kile/latex it prodoces nice
results but I haven't mastered it fully yet.
Finally I'm sure I read on the list sid is more suitable for amd than
sarge.
Gavin



On Mon, 2005-04-11 at 11:11 +0200, Alexander Nagel wrote:
> Hi list,
> i have a strange dependency problem with my fresh install in sarge but 
> in sid everything seems to be fine. It is ok to switch to sid? It is 
> stable enough to run GNOME with Firefox, Thunderbird, Abiword as main 
> applications?
> Thanks for your comments
> Alex
> 
> 


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

Some mails I forgot to submit to list...

[james]

I've noticed I've forgotten to send some mails to the list today (duh)... If 
anyone notices any mails from me not CC'ed/TO'ed the list, please Fwd it to the 
list, as I'm using webmail at the moment, so can't get them back :(

Sorry guys! :(
James

___
Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net



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

Re: Muse, QJackctl etc. problems

[james]

Hi again Daniel,

Yes, I'm thinking it could be a problem in the app itself rather than something 
configured incorrectly... all other progs (Ardour, Jack, qjackctl, jack-rack 
etc.) all work fine now, except for this. I'll get in touch with the muse list 
to see if anyone might have an idea!!

Many cheers,
James

Daniel James <[EMAIL PROTECTED]> wrote :

> Hi James,
> 
> > no locale /
> > panic: alloc 56
> > Segmentation fault
> 
> I tried it on a non-Debian machine (Mandrake 10.1) to see if this is a 
> packaging or upstream problem. I got:
> 
> no locale /
> open projectfile: No such file or directory
> starting with default template
> cannot set tick on /dev/rtc: Invalid argument
> precise timer not available
> 
> Muse then quits, no segfault though.
> 
> I also get the locale warning from qjackctl but that runs fine, so I 
> think the missing en_GB locale is a red herring. I think your best 
> bet is to ask the Muse developers on their mailing list.
> 
> Sorry not to be more helpful...
> 
> Daniel

___
Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net



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

Re: Is sid ok??

[james]

I use sarge at home, I've not had any real problems with it. I use firefox, 
thunderbird, abiword and amsn (and some music production apps, such as Ardour 
and Jack), and I've not had a problem with dependancies...

I've not had any experience with sid, so I can't speak for it. The only problem 
with my system is random freezing, but apparently that is down to my graphics 
drivers...

Alexander Nagel <[EMAIL PROTECTED]> wrote :

> Hi list,
> i have a strange dependency problem with my fresh install in sarge but 
> in sid everything seems to be fine. It is ok to switch to sid? It is 
> stable enough to run GNOME with Firefox, Thunderbird, Abiword as main 
> applications?
> Thanks for your comments
> Alex
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

___
Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net



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

Re: Nvidia problems... again

[james]

Is this in a pure64 environment, or in a 32-bit chroot?

Also, could you send a link to where these binaries are distributed? I might 
have a play around once my graphics drivers work (being presumptious that 
they'll actually work in the end ;) ...)

Cheers,
James

NaiosKAE{FR} <[EMAIL PROTECTED]> wrote :

> Hi
> I use a differnet way to play
> 
> for instance, I have Doom3, Ut2003 & Ut2004, NeverWinterNight, RTCW, 
> Medal of honnor, ... running under Debian. I'm using linux binary files 
>to play (loki has most of them). first install the game trough wine 
> (not winex) then copy data tree to your game location, copy or install 
> teh linux binaries then chown user.grp (by default root.staff with linux 
> installers, i moved them to root.games) then chmod 750. finally enjoy 
> the game. (that don't work for all the game, for instance warhammer40K 
> has no linux binary files at this time)
> [...]
> 
> --
> NaiosKAE{FR}
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

___
Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net



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

Is sid ok??

[Alexander Nagel]

Hi list,
i have a strange dependency problem with my fresh install in sarge but 
in sid everything seems to be fine. It is ok to switch to sid? It is 
stable enough to run GNOME with Firefox, Thunderbird, Abiword as main 
applications?
Thanks for your comments
Alex

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

Re: Installer and installed system differ in disk enumeration

[A.E.Lawrence]

aiyama wrote:
(B> There are at least 2 ways to complete installation.
(B> 
(B> 1. Using default kernel: Have you selected a non-default kernel?  Choose
(B> default like kernel-image-2.6-amd64, but not 2.6.9-10-amd64.
(B> 
(B> 2. Using chroot:  Install mini 64-bit system to one of PATA  disk: /dev/hda
(B> through hdd.  Then using the mini-system edit /etc/lilo.conf to suit your
(B> particular setting, and
(B> # sbin/lilo -C etc/lilo.conf -v
(B> I do not know grub, but you can do it similar way.
(B
(BThe problems arise before those options are available :-( But it is
(Bpossible to use grub's editing options to get an initial system. Then
(Bone can edit the grub configuration and /etc/fstab to match whichever
(Bkernel is loaded. The point is that the installer is setting these
(Bthings up incorrectly. Short of using something like disc labels or
(Bsomehow ensuring that all kernels agree on enumeration in all
(Bcircumstances, there doesn't seem to be an easy solution.
(B
(Bael
(B
(B
(B-- 
(BTo UNSUBSCRIBE, email to [EMAIL PROTECTED]
(Bwith a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Nvidia problems... again

[Daniel James]

Hi James,

> I'm happy using Wine to use my standard Windoze programs (Adobe
> Photoshop and the likes... unfortunately my work has to use PSDs
> all the time, so I'm kinda stuck..

I personally haven't had any problems with the PSD support in The 
Gimp, but then I don't use PSD every day.  

From: http://docs.gimp.org/en/go01.html

PSD is Adobe Photoshop's native file format, and thus is comparable to 
XCF in complexity. Gimp's ability to handle PSD files is 
sophisticated but limited: some features of PSD files are not loaded, 
and only PSD versions XX or less are supported. Unfortunately, Adobe 
has now made the Photoshop Software Development Kit ­ which includes 
their file format specifications ­ proprietary, and only available to 
a limited set of developers blessed by Adobe. This does not include 
the Gimp development team; and the lack of information makes it very 
difficult to maintain up-to-date support for PSD files. 
 
Cheers

Daniel


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

Re: Nvidia problems... again

[NaiosKAE{FR}]

Hi
I use a differnet way to play
for instance, I have Doom3, Ut2003 & Ut2004, NeverWinterNight, RTCW, 
Medal of honnor, ... running under Debian. I'm using linux binary files 
  to play (loki has most of them). first install the game trough wine 
(not winex) then copy data tree to your game location, copy or install 
teh linux binaries then chown user.grp (by default root.staff with linux 
installers, i moved them to root.games) then chmod 750. finally enjoy 
the game. (that don't work for all the game, for instance warhammer40K 
has no linux binary files at this time)
[...]

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

Re: Muse, QJackctl etc. problems

[Daniel James]

Hi James,

> no locale /
> panic: alloc 56
> Segmentation fault

I tried it on a non-Debian machine (Mandrake 10.1) to see if this is a 
packaging or upstream problem. I got:

no locale /
open projectfile: No such file or directory
starting with default template
cannot set tick on /dev/rtc: Invalid argument
precise timer not available

Muse then quits, no segfault though.

I also get the locale warning from qjackctl but that runs fine, so I 
think the missing en_GB locale is a red herring. I think your best 
bet is to ask the Muse developers on their mailing list.

Sorry not to be more helpful...

Daniel


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

Re: Installer and installed system differ in disk enumeration

[aiyama]

There are at least 2 ways to complete installation.
(B
(B1. Using default kernel: Have you selected a non-default kernel?  Choose
(Bdefault like kernel-image-2.6-amd64, but not 2.6.9-10-amd64.
(B
(B2. Using chroot:  Install mini 64-bit system to one of PATA  disk: /dev/hda
(Bthrough hdd.  Then using the mini-system edit /etc/lilo.conf to suit your
(Bparticular setting, and
(B# sbin/lilo -C etc/lilo.conf -v
(BI do not know grub, but you can do it similar way.
(B
(BGood luck to your effort.
(B
(B
(B-- 
(BTo UNSUBSCRIBE, email to [EMAIL PROTECTED]
(Bwith a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Nvidia problems... again

[james]

I use a program called Cedega (wrapped by a GUI called Point-to-Play). I don't 
really play games much, but I wanted to try it out on Linux, and apparently 
this program is "the dog's bollocks".

It appears otherwise, the only game I could get working was BG2 (without the 
exansion, however). I tried Diablo 2 (one of their "supported" games), failed, 
I tried Diablo 1 (which also works), Half-life works to a certain degree, 
Discworld Noir doesnt work, Splinter Cell: Pandora Tomorrow doesn't work, 
Enclave doesn't work, and a few others which I tried didn't work.

Altogether, it seems fairly unsuccessful, but I didn't put much effort into 
it... kind of a "if it doesn't work first time, give up" case, as I'm not a 
big-time video gamer :)

If you are interested, there's a small fee for a 3-month sign up to recieve 
support, access to the forum and so on, its about £9GBP I think. I wouldn't 
recommend it for people like myself, but if you really want to game, and you're 
willing to put a bit of effort into configuring it properly, then I'd say give 
it a go!

Link to the site is:
http://www.transgaming.com/
Cedega - their version of Wine, powered for Windows games
Point-to-Play - a nice GUI wrapper for Cedega, I'd advise just downloading P2P, 
and installing Cedega through that, as it does the configuration for you. It 
also helps with organising your games.

Bear in mind there's a lot more work trying to get it working on an amd64 
machine, as a fully working chroot (with /home and /tmp bind mounted, 32-bit 
versions of your graphics drivers installed into your chroot on your amd64 
machine are required alsoe etc.), but if you're on a x86 machine, the setup 
should be fairly simple.

But for now, I'm happy using Wine to use my standard Windoze programs (Adobe 
Photoshop and the likes... unfortunately my work has to use PSDs all the time, 
so I'm kinda stuck.. but at least I can use linux :))

Hope this helps,
James

Javier Kohen <[EMAIL PROTECTED]> wrote :

> El dom, 10-04-2005 a las 20:17 +0100, James Titcumb escribió:
> 
> > I would use nv driver (I am using it now actually), but I have two 
> > monitors, and its pointless having 2 LCD screens, when you can only use
> 
> > one of them! AFAIK, the only driver that supports dual screens is the 
> > nvidia and ATI ones... if you know different, let me know how to do it!
> 
> > I don't really do graphic intensive stuff (I might occasionally play 
> > Baldur's Gate, but that's not exactly video-hungry!), so if its not a 
> > high-performance driver, I'm not hugely bothered. As long as I get 
> > smooth standard usage, I'm ok :)
> 
> Hi, I'm replying off list because I'm interested in knowing how you play
> Baldur's Gate on Linux.
> 
> Thanks :)
> 
> -- 
> Javier Kohen <[EMAIL PROTECTED]>
> ICQ: blashyrkh #2361802
> Jabber: [EMAIL PROTECTED]

___
Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net



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

Re: Nvidia problems... again

[james]

Hi David, that could be useful, I shall give that a go when I get home from 
work tonight and report what happens. I've disabled rivafb (due to the nvidia 
driver conflict), so I'll have to rebuild the keernel, but I'll do it tonight, 
and let you know how I get on!

Cheers,
James

David Liontooth <[EMAIL PROTECTED]> wrote :

> James Titcumb wrote:
> 
> >
> >> I would ask on the nVidia Linux Forum 
> >> http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14
> >
> >
> > They don't seem to be very responsive, unlike here :)
> >
> >>
> >> That said, if you're trying to troubleshoot, why not use the nv 
> >> driver? It's
> >> excellent for 2D work.
> >
> >
> > I would use nv driver (I am using it now actually), but I have two 
> > monitors, and its pointless having 2 LCD screens, when you can only 
> > use one of them! AFAIK, the only driver that supports dual screens is 
> > the nvidia and ATI ones... if you know different, let me know how to 
> > do it! I don't really do graphic intensive stuff (I might occasionally 
> > play Baldur's Gate, but that's not exactly video-hungry!), so if its 
> > not a high-performance driver, I'm not hugely bothered. As long as I 
> > get smooth standard usage, I'm ok :)
> 
> 
> Well, nv supports dual screens using the xinerama option in XFree86. 
> 
> It's not clear the driver supports "dual head" where you have two 
> VGA
> 
> ports on one video card -- Alex Deucher claimed a year ago it was not 
> supported 
> (http://lists.freedesktop.org/pipermail/xorg/2004-May/000685.html).
> 
> But it does support the "xinerama" option where you have two video
> 
> cards. See for example 
> http://krampus.phys.uconn.edu/computers/FAQ/xinerama.html
> 
> >
> > The thing that's strange, is that previous to building the 2.6.11 
> > kernel up (when i was on 2.6.10), the nvidia driver built + installed 
> > fine, but now it doesn't... perhaps it's a disagreement with the 
> > 2.6.11 kernel??
> 
> I don't think that sounds particularly farfetched -- the nvidia drivers 
> routinely fail to work on new kernels, and need patches.
> 
> But what about the framebuffer driver? I was amazed to discover that 
> it's perfectly happy driving x-windows, including dual monitors, but I 
> haven't tried it on an amd64.
> It would be great if you could find out if it works there -- though I 
> can't promise you it'll be worth your time! Here's what you need:
> 
>  * Compile framebuffer support in the kernel
> 
> I was using rivafb, which is likely all you have also in the 2.6.11 
> kernel. In 2.6.12-rc there's a new one called nvidiafb, looks promising.
> 
>  * After booting, remove the nvidia module (it's not compatible with 
> rivafb) and load
> 
> rmmod nvidia && modprobe fbcon && modprobe rivafb &&
> fbset fullscreen 
> (see below for setup)
> 
> Contacts:
> 
> * rivafb is maintained by Ani Joshi and lately worked on by Antonino
>   A. Daplas (who also wrote the new nvidiafb)
> * [EMAIL PROTECTED]
>   ;
> * [EMAIL PROTECTED]
> 
> Commands:
> 
> * more /proc/fb   list current frame buffer device information
> * fbset -i   shows current framebuffer configuration
> * fbset -x  shows xfree configuration
> * mplayer -vo directfb 
> * fbxine 
> * fbi *.jpg -t 5 -autozoom -edit
> * Snapshot of the frame buffer content: cp /dev/fb0 myfile
> * man fb.modes
> * modeline2fb (for creating entries in /etc/fb.modes)
> 
> To create the correct modeline, issue
> 
> modeline2fb /etc/X11/XF86Config
> 
> I edited /etc/fb.modes, adding
> 
> #  Generated using modeline2fb, 1280x854, 85.266 MHz dotclock
> 
> mode "fullscreen"
>   geometry   1280 854   1280 26201   8
>   timings11728   240 16   31 0   256 7
>   hsync low
>   vsync low
> endmode
> 
> This is activated by the "fbset fullscreen" command.
> 
> In XF86Config-4 use
> 
> Driver  "fbdev"
> 
> Worked for me. For dual monitors, you'll have to use the xinerama 
> option, as with nv.
> 
> The framebuffer stuff is very cool, but fiddley still. The quality is 
> excellent.
> Keep us posted if you try this on amd64.
> 
> Dave

___
Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net



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