Re: unreal tournament 2004 for x86_64 on debian
it would seem the problem is audio related as turning audio explicitly off in the ut2004.ini file allows the game to run (huray) albiet with no sound. although it only runs first time (ie it segfaults then page faults the kernel if you quit and run again) anyway so now to fight with openal and possibly sdl i have ut2004's provided libSDL moved and then replaced with a link to the debian supplied libSDL in /usr/lib. initially it included libsdl-oss. my computer was completely crashing and rebooting i removed libsdl-oss and wacked on libsdl-alsa (as im using alsa sound). now the pc is just freezing with a black screen. in both cases ive liked the ut2004 openal.so to the debian supplied libopenal.so in /usr/lib i imagine i need to configure it more and also i wouldnt be suprised if there is something wrong with the sound card drivers as its an onboard realtek and the drivers for it have improved considerably over the last few kernel releases. ie no support in 2.6.8, generic recognition and support in 2.6.11 and 12 and now in 14 it seems to realise its an nforce'd realtek chip. (CK804) any help would be nice and muchly appreciated Dean Robert Isaac wrote: $ ldd ut2004-bin-linux-amd64 libdl.so.2 => /lib/libdl.so.2 (0x2abc1000) libpthread.so.0 => /lib/libpthread.so.0 (0x2acc5000) ./libSDL-1.2.so.0 => ./libSDL-1.2.so.0 (0x2add9000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x2af33000) libm.so.6 => /lib/libm.so.6 (0x2b111000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2b297000) libc.so.6 => /lib/libc.so.6 (0x2b3a2000) /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x2aaab000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x2b5e2000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x2b7c) To run ut2004 as a 64 bit native program you need the two community bonus packs installed along with the latest patches. Install the patches after the bonus packs. torrents for the bonus packs can be found here: http://liflg.org/ download the patches from here: http://www.unrealtournament.com/ut2004/downloads.php On 10/28/05, Dean Hamstead <[EMAIL PROTECTED]> wrote: the nvidia driver use 'nvidia' as their driver get 7676 from http://people.debian.org/~rdonald youll have to build them entirely from source debs (no dramas). also go get teh patches from the nvidia forums and apply them to the nv folder before you build the nvidia-kernel-modules youll need too apply then with patch -p1 patch.txt (to drop a level or directories) and then re tar them into nvidia-kernel-source.tar.gz (as module-assistant will untar it again) you can build q3a from source (worth it imo) and it will generate x86_64 binaries however im still looking for someone to produce an 'ldd ut2004-bin' for me please so i cant see what versions are used. someone who gets ut to run please!! Dean Alan Ianson wrote: On Fri October 28 2005 12:02 pm, Mike Dobbs wrote: I installed the nvidia driver using m-a install nvidia ( I think I had the 7474 nvidia-modules installed, make sure nvidia-glx is the same, also install nvidia-glx-ia32 for 32 bit support). Then xorg needs some changes too, google amd64 debian nvidia. Will do. Does running ut2004 produce anything in the terminal window? You mean from an "ALT-F# terminal/console. I have not tried. I've always had to run these sort of things from x-windows. Running from a terminal would be best I suspect, if the game supports it I will run it from there and see what happens. Are you trying to run ut2004 in 32 bit mode or 64 bit? Originally I just ran it from the desktop icon that was created (if I remember correctly). I never knew there was a 64bit version. I don't have a chroot here but I do have ia32 libs installed so I do get some 32 bit apps to run. If there is a 64 bit version I would run that, but if not I'd have to run the 32 bit if I can get compatibility. - Original Message - From: "Alan Ianson" <[EMAIL PROTECTED]> To: Sent: Friday, October 28, 2005 1:34 PM Subject: Re: unreal tournament 2004 for x86_64 on debian On Fri October 28 2005 11:05 am, Mike Dobbs wrote: What errors are you getting? After I installed the latest update it stopped working. The window would show up on the taskbar with a spinning hourglas for about 15 seconds and then just went away. I'm not sure what was wrong. Make sure your version of the nvidia modules matches your versoin of the nvidia-glx. OK, I'm going to try and install now. Do these nvidia modules work with the "nv" driver I am using now, or do I need to get/build a new "nvidia" driver for the xorg config? I had to link the openal library to use the 64bit system library. I will have to do that too I think, how would I do that? - Original Message - From: "Alan Ianson" <[EMAIL PROTECTED]> To: Sent: Friday, October 28, 2005 1:01 PM
Re: How to set default compiler to 4.0?
Lennart Sorensen wrote: > Or you could start running unstable where gcc-4.0 is the default I > believe. :) Same with testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Highly Recommended Cailis Xb6Tdc
High quality Caiilis available at affordable price. Only $3.99 per tabls which last you 36 hours of e rectiions Try us out today... http://de.geocities.com/Piggy41798Claudette78253/ 1FDAF5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eeyes
also, if you have imagemagick installed (likely you do) then 'display' isnt half bad. beats viewing an image with vi. Dean Larry Doolittle wrote: On Mon, November 7, 2005 10:47 pm, Olivier Bornet said: I often use eeyes (http://packages.debian.org/oldstable/graphics/eeyes). Is someone knowing if there is a amd64 package for it ? (or even if it is replaced by another tool on the Debian repositories). Reply by Dean Hamstead: check out gqview The intended Gnome standard is now "eog" (Eye of Gnome). I personally use "qiv" (Quick Image Viewer). Both are supported Debian packages. - Larry -- 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]
gl-117 won't work: segfault when moving mouse
Hi I can start gl-117 without any problem. If I move the mouse, however, it crashes after a second or so. I even can't stop X.Org with Control-Alt-Bachspace or switch to a console with Alt-F1. The only possibility is the Reset-Button or to start sleep 60; killall -9 gl-117 before starting gl-117. Here are the important messages shown after starting with -d5: Debug: Entering SDL main loop (GLUT emulation) Debug: Manoever: Immelmann Debug: Manoever: Immelmann Fatal signal: Segmentation Fault (SDL Parachute Deployed) Please tell me if you want the whole output; however, it doesn't look interesting to me. When starting gl-117 within a i386-chroot, this doesn't happen. First I thought of a SDL problem, but other SDL games such as foobillard work What can I do to make it work? Bye Gian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit emu packs
> Ok, tested skype some more. > Strange effects here. While it starts in KDE the small "S" Icon junping > around for a LONG time, as if it still tries to access some data. Skype > is available and running and the small icon still jumps on... > Any ideas? I think is related to KDE, but not to 32bit. > AND: I can use skype fairly normal, but skype won't close the sound > device after accessing the microphone. > I used the "echo123" user - til the point the microphone is activated, I > can cancel the call and start it again with no problem (I get the sound > of the hangup). > But as soon as the microphone is activated, I don't get the hungup sound > and a retry tells me "problem with sound device". > Strange... If you look on my page you'll understand why. Skype for Linux is crappy. I hope Openwengo development won't take so much. However thanks for testing!
Re: Software RAID, LVM, and LILO on amd64 sarge
On Mon, Nov 07, 2005 at 09:04:08AM +, A J Stiles wrote:
> If you are using software RAID then you must have a /boot partition which is
> a
> non-RAID, ext3 or ext2 partition; and a separate swap partition on each drive
>
Note that this isn't true for RAID1 (mirroring); LILO can load the
kernel directly from that.
> {you don't need RAID on swap; if that goes down, the kernel's going down
> anyway. Not to mention it's a serious performance issue}. Note, the
RAID1 on swap means a failed disk should not take the kernel down.
I'm using it here, although I also have enough RAM that I shouldn't
need to swap very often.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: beta status
On Sat, Nov 05, 2005 at 03:19:06PM +0100, Kurt Roeckx wrote: > On Sat, Nov 05, 2005 at 12:22:49AM +0100, Kurt Roeckx wrote: > > > > The problem now seems to be that rootskel-locale still seems to > > exist in testing for some reason. It's unclear to me why it > > still exists. This is causing the monolithic target to fail to > > build because it can't find the locale. > > The next problem is to actually get it into the archive. It's > getting rejected: > Rejected: debian-installer-images_20051026_amd64.tar.gz: changes file doesn't > say debian-installer-images_20051026 for Source > Rejected: debian-installer-images_20051026_amd64.tar.gz: should be 20051026 > according to changes file. > Rejected: debian-installer-images_20051026_amd64.tar.gz: changes file doesn't > list `source' in Architecture field. The tar has now been manually extracted and available. The .deb package isn't installed yet however, we'll get back to that later. The netinst build should now be buildable. There is a proposed patch amd64.debian.net/~aba/diff.jennifer that should fix this in the future, and hopefully get applied soon. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: beta status
Kurt Roeckx wrote: > Rejected: debian-installer-images_20051026_amd64.tar.gz: changes file doesn't > list `source' in Architecture field. Second try.. this seems like it's expecting a sourceful upload for some reason, which it shouldn't if you have the debian-installer source package already in the repository from the main debian repo. -- see shy jo signature.asc Description: Digital signature
Re: eeyes
On Mon, November 7, 2005 10:47 pm, Olivier Bornet said: > I often use eeyes > (http://packages.debian.org/oldstable/graphics/eeyes). > Is someone knowing if there is a amd64 package for it ? (or even if it > is replaced by another tool on the Debian repositories). Reply by Dean Hamstead: > check out gqview The intended Gnome standard is now "eog" (Eye of Gnome). I personally use "qiv" (Quick Image Viewer). Both are supported Debian packages. - Larry signature.asc Description: Digital signature
Re: OpenOffice e outros.
Vê com essa documentaçao : http://lists.debian.org/debian-amd64/2005/07/msg00663.html On Fri, 2005-11-04 at 11:16 -0300, Pedro Henrique de Lira wrote: > Olá pessoal, blz. > > então adquiri recentemente um notebook com AMD64, baixei o iso do > Debian AMD64, (falta o segundo DVD ainda) e já estou curtindo muito, > mas tenho dúvida sobre aplicativos que usava e desejo usar, ele só > roda programas compilados para 64bits? gostaria de instalar o > OpenOffice, mas ele não aceita os pacotes i386, será que o único jeito > e baixar o fonte e recompilar e outros programas mesmo procedimento? > > []s > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with > a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] -- FATAL ERROR! SYSTEM HALTED! - Press any key to do nothing... -- José-Pedro Machado - <[EMAIL PROTECTED]> FT/SCR/HDI/DTQ/Hebex/Sophia - Sophia Antipolis - France Tl. : 04 92 28 81 79 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
On Nov 7, 2005, at 3:04 AM, A J Stiles wrote:
On Saturday 05 November 2005 00:22, Thomas F. O'Connell wrote:
On Nov 4, 2005, at 5:37 PM, Thomas F. O'Connell wrote:
On Nov 4, 2005, at 4:38 PM, Gilles wrote:
During partitioning, I set up both software RAID1 and LVM. After
partitioning, I tried to install LILO in the MBR on /dev/md0,
but it
didn't work. I tried advanced mode and tried /dev/mapper/vg-
root as
an installation target, but that was invalid, as well.
I think that you have to use an actual disk or disk partition as
target.
At least, that's how I did it with "grub" where a disk is
specified with
something like "(hd0)" and a partition as "(hd0,0)".
To have the loader available, even if one of the disks in the array
fails, you just install it on every disks that composes "/dev/md0".
I thought I had read that grub didn't play well with sarge.
Unfortunately, now I'm struggling even to get RAID1 set up the way
I'd like, even without LVM.
Maybe this is about the methodology I'm using rather than a problem
with the installer, although I would expect the installer to be a
little more intuitive. I have a two-drive machine (two 250 GB
drives), and I'd like to configure them in a RAID1 such that each
disk is bootable.
I thought that I could just configure each disk with a single
physical RAID volume partition and then create a software RAID in
which I could create as many partitions as I want, including a /
boot partition if need be.
But I'm running into issues with seeing the remainder of the disk
space be flagged as "unusable" as soon as I create a partition in
the RAID1.
Okay. Sorry for the noise of my reply. I read this a little more
closely:
http://www.tldp.org/HOWTO/Software-RAID-HOWTO-11.html#ss11.1
But this leaves me with my original problem.
What I'm doing now is:
1. Set up a monolithic physical volume for RAID on each disk.
2. Configure RAID1 using these volumes.
3. Configure a single LVM volume group (vg) with four logical volumes
in it: root, swap, var, and home. I don't specifically create a
volume or mount point for /boot, but I haven't gathered that that
should be necessary.
This isn't specific to 64-bit systems. Basically, a bootstrap
loader such as
LILO has only a very primitive filesystem; it expects the kernel to
be in a
contiguous group of sectors on a single disk. Only once the kernel is
loaded, decompressed and running do the other, more complex file
systems
become available.
If you are using software RAID then you must have a /boot partition
which is a
non-RAID, ext3 or ext2 partition; and a separate swap partition on
each drive
{you don't need RAID on swap; if that goes down, the kernel's going
down
anyway. Not to mention it's a serious performance issue}. Note, the
bootstrap loader *doesn't* care about / -- when you configure it by
running /sbin/lilo, the kernel is already running, and it will be
able to
find the sector where the kernel begins. So your root partition
can {and
probably should} be RAID.
Build your system with a few megs ext3 / ext2 partition near the
beginning,
then a gig or so of swap {remember you will have 2 swap files, 1
on each
drive} and then your main partitions. Once your system is
installed then
you will have a boot partition on sda1 but not on sdb1. So you now
should
copy over the contents of sda1 to sdb1 using dd. In effect you are
doing
RAID manually! But this only needs to be done whenever you compile
a new
kernel.
Well, the funny thing is that last night, as I was about to dig into
manual intervention, I got the sarge amd64 installer to set things up
according to my ideal, and it seems to have worked.
I'm going to verify that I can boot by either drive today, but I
must've crossed my fingers just right during partitioning. In all
seriousness, it's possible (read: likely) that there was a detail
about one of the partitions I had attempted to setup that was
configured improperly during my previous experimentation with the
sarge installer.
Granted, I think it'd be wonderful if the installer eventually makes
the process a little more failsafe (while preserving flexibility),
but I guess that's what software development is about... :P
At the moment, though, I'm running sarge amd64 with two RAID1s, one
of which is using /boot as a mount point and one of which is a
physical volume for LVM, and this is just what I want.
--
Thomas F. O'Connell
Database Architecture and Programming
Co-Founder
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [pgadmin-support] PgAdmin 1.4.0 Debian SArge AMD64 debs available
Dave Page wrote: >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On Behalf Of >>Joost Kraaijeveld >>Sent: 07 November 2005 11:56 >>To: Debian-Amd64; PgAdmin-support >>Subject: [pgadmin-support] PgAdmin 1.4.0 Debian SArge AMD64 >>debs available >> >>Hi, >> >>I compiled PgAdmin 1.4.0 *OOTB* and packaged them into Debian >>installable .deb files. > > > OOTB? With no changes to keywords.c? > > >>These files are *not* made by an official Debian Maintainer. I just >>created them so I could easily install PgAdmin on several Debian Sarge >>AMD64 boxes. >> >>They are available at http://petitbonum.askesis.nl/pgadmin/. >>They will >>be available until an official Debian repository contains the >>packages. >>Or untill I go bankrupt, whatever comes first ;-) Hi Joost, thanks for your work, however I have some doubt concerning installation of your packages on a pure Sarge system. Your debs depend on libpq4 and libwxgtk2.6-0. Neither the former nor the latter are included with Sarge. Did you use backport of them or simply backported these two packages too? Maybe you used a mixed Sarge+testing/unstable environment to build the packages? Another thing, the version you used for the packages clashes with my versionning scheme and it does not include a debian revision which should definitely be added in the case of pgadmin3 package. I'm about to upload unofficial packages to pgadmin.org and will ask my sponsor for an upload of official packages to debian.org until the end of the week. If you agree, I'll ask you for a build of my unofficial packages on amd64 for sarge after these uploads so that our users can benefit from your build. IMHO we should leave [EMAIL PROTECTED] as all of this is really pgadmin3 related. Regards, Raphaël -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eeyes
i used to be a fan of it, but it seems to have disappeared for whatever reason. check out gqview Dean On Mon, November 7, 2005 10:47 pm, Olivier Bornet said: > Hello, > > I often use eeyes (http://packages.debian.org/oldstable/graphics/eeyes). > > Is someone knowing if there is a amd64 package for it ? (or even if it > is replaced by another tool on the Debian repositories). > > Thanks in advance. > > Olivier > -- > Olivier Bornet|français : http://puck.ch/f > Swiss Ice Hockey Results |english : http://puck.ch/e > http://puck.ch/ |deutsch : http://puck.ch/g > [EMAIL PROTECTED]|italiano : http://puck.ch/i > Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/ > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit emu packs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 v0n0 wrote: > Hi, I've "repacked" some 32bit libraries for Debian amd64 system, and > Skype and Wine. Skype is running fine, Wine executes, but gives (me) > error on some folders. These are very experimental, but since they don't > mess system, you may want to give it a try! ;) > More infos at: > http://v0n0.altervista.org/ Ok, tested skype some more. Strange effects here. While it starts in KDE the small "S" Icon junping around for a LONG time, as if it still tries to access some data. Skype is available and running and the small icon still jumps on... Any ideas? AND: I can use skype fairly normal, but skype won't close the sound device after accessing the microphone. I used the "echo123" user - til the point the microphone is activated, I can cancel the call and start it again with no problem (I get the sound of the hangup). But as soon as the microphone is activated, I don't get the hungup sound and a retry tells me "problem with sound device". Strange... I use the Asus A8N SLI premium with the nforce4 chipset and kernel 2.6.12. Maybe I should try the 2.6.14 kernel... Cya Lars - -- - - TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel.: +43 316 873-5405 E-Mail: [EMAIL PROTECTED] PGP-Key-ID: 0xB87A0E03 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDb0+2VguzrLh6DgMRAviwAJ93AsV3K6Sde7eOaKfjVKmvUAkU3wCfZfp9 tShiLaDpkJlk2xVYZwvWVQY= =KEmS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: [pgadmin-support] PgAdmin 1.4.0 Debian SArge AMD64 debs available
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Joost Kraaijeveld > Sent: 07 November 2005 11:56 > To: Debian-Amd64; PgAdmin-support > Subject: [pgadmin-support] PgAdmin 1.4.0 Debian SArge AMD64 > debs available > > Hi, > > I compiled PgAdmin 1.4.0 *OOTB* and packaged them into Debian > installable .deb files. OOTB? With no changes to keywords.c? > These files are *not* made by an official Debian Maintainer. I just > created them so I could easily install PgAdmin on several Debian Sarge > AMD64 boxes. > > They are available at http://petitbonum.askesis.nl/pgadmin/. > They will > be available until an official Debian repository contains the > packages. > Or untill I go bankrupt, whatever comes first ;-) Great, thanks. I'd normally offer to host them for you, but I know that Raph does some magic with the apt stuff for Debian in our ftp area. I'll leave it to him to speak to you about what he might want to do with your builds :-) Regards, Dave.
PgAdmin 1.4.0 Debian SArge AMD64 debs available
Hi, I compiled PgAdmin 1.4.0 *OOTB* and packaged them into Debian installable .deb files. These files are *not* made by an official Debian Maintainer. I just created them so I could easily install PgAdmin on several Debian Sarge AMD64 boxes. They are available at http://petitbonum.askesis.nl/pgadmin/. They will be available until an official Debian repository contains the packages. Or untill I go bankrupt, whatever comes first ;-) -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 e-mail: [EMAIL PROTECTED] web: www.askesis.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
eeyes
Hello, I often use eeyes (http://packages.debian.org/oldstable/graphics/eeyes). Is someone knowing if there is a amd64 package for it ? (or even if it is replaced by another tool on the Debian repositories). Thanks in advance. Olivier -- Olivier Bornet|français : http://puck.ch/f Swiss Ice Hockey Results |english : http://puck.ch/e http://puck.ch/ |deutsch : http://puck.ch/g [EMAIL PROTECTED]|italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/ signature.asc Description: Digital signature
Re: Trying to build OOo2 in an x86 chroot
On Fri, 4 Nov 2005, Jerome Warnier wrote: I'm trying to backport OOo2 to Sarge for x86 on a Debian Sarge for AMD64. I setup a chroot which works perfectly: $ dpkg --print-architecture i386 But still, the build fails like this: ERROR: Error 65280 occurred while making /root/openoffice.org-2.0.0/ooo-build/build/ooo680-m3/sal/rtl/source make[1]: *** [stamp/build] Error 1 make[1]: Leaving directory `/root/openoffice.org-2.0.0/ooo-build' make: *** [debian/stampdir/build] Error 2 I have been trying to backport OOo2 as you, ran into the same problem and was able to proceed past this by installing and using the "linux32" package. Nonetheless, I stumbled upon another problem down the way, therefore I would be very interested to know if you can complete the build. Bye Giacomo -- _ Giacomo Mulas <[EMAIL PROTECTED]> _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _ -- Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi da MailScanner, ed e' risultato non infetto. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nvidia (graphics) driver pain
On Fri, 4 Nov 2005, Lennart Sorensen wrote: Well as I said, the nv driver does not have problems with some fb drivers, while nvidia driver always does. Well, frequently but not always: I administer a bunch of amd64 workstations and all of them have nvidia graphic cards, use the nvidia driver _and_ the vesa fb, built into the kernel and selecting a well defined vesa mode at boot. I never experienced a problem with this. Maybe I was just lucky. On the other hand, I could not use the same setup with my amd64 laptop: if I try it boots flawlessly, but the vesa graphics modes are not compatible with my lcd display, therefore I get a blank screen until kdm starts, and the console is unusable. The nvidia driver _is_ incompatible with the nvidiafb driver, though. Bye Giacomo -- _ Giacomo Mulas <[EMAIL PROTECTED]> _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _ -- Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi da MailScanner, ed e' risultato non infetto. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
On Saturday 05 November 2005 00:22, Thomas F. O'Connell wrote:
> On Nov 4, 2005, at 5:37 PM, Thomas F. O'Connell wrote:
> > On Nov 4, 2005, at 4:38 PM, Gilles wrote:
> >>> During partitioning, I set up both software RAID1 and LVM. After
> >>> partitioning, I tried to install LILO in the MBR on /dev/md0, but it
> >>> didn't work. I tried advanced mode and tried /dev/mapper/vg-root as
> >>> an installation target, but that was invalid, as well.
> >>
> >> I think that you have to use an actual disk or disk partition as
> >> target.
> >> At least, that's how I did it with "grub" where a disk is
> >> specified with
> >> something like "(hd0)" and a partition as "(hd0,0)".
> >> To have the loader available, even if one of the disks in the array
> >> fails, you just install it on every disks that composes "/dev/md0".
> >
> > I thought I had read that grub didn't play well with sarge.
> >
> > Unfortunately, now I'm struggling even to get RAID1 set up the way
> > I'd like, even without LVM.
> >
> > Maybe this is about the methodology I'm using rather than a problem
> > with the installer, although I would expect the installer to be a
> > little more intuitive. I have a two-drive machine (two 250 GB
> > drives), and I'd like to configure them in a RAID1 such that each
> > disk is bootable.
> >
> > I thought that I could just configure each disk with a single
> > physical RAID volume partition and then create a software RAID in
> > which I could create as many partitions as I want, including a /
> > boot partition if need be.
> >
> > But I'm running into issues with seeing the remainder of the disk
> > space be flagged as "unusable" as soon as I create a partition in
> > the RAID1.
>
> Okay. Sorry for the noise of my reply. I read this a little more
> closely:
>
> http://www.tldp.org/HOWTO/Software-RAID-HOWTO-11.html#ss11.1
>
> But this leaves me with my original problem.
>
> What I'm doing now is:
>
> 1. Set up a monolithic physical volume for RAID on each disk.
> 2. Configure RAID1 using these volumes.
> 3. Configure a single LVM volume group (vg) with four logical volumes
> in it: root, swap, var, and home. I don't specifically create a
> volume or mount point for /boot, but I haven't gathered that that
> should be necessary.
This isn't specific to 64-bit systems. Basically, a bootstrap loader such as
LILO has only a very primitive filesystem; it expects the kernel to be in a
contiguous group of sectors on a single disk. Only once the kernel is
loaded, decompressed and running do the other, more complex file systems
become available.
If you are using software RAID then you must have a /boot partition which is a
non-RAID, ext3 or ext2 partition; and a separate swap partition on each drive
{you don't need RAID on swap; if that goes down, the kernel's going down
anyway. Not to mention it's a serious performance issue}. Note, the
bootstrap loader *doesn't* care about / -- when you configure it by
running /sbin/lilo, the kernel is already running, and it will be able to
find the sector where the kernel begins. So your root partition can {and
probably should} be RAID.
Build your system with a few megs ext3 / ext2 partition near the beginning,
then a gig or so of swap {remember you will have 2 swap files, 1 on each
drive} and then your main partitions. Once your system is installed then
you will have a boot partition on sda1 but not on sdb1. So you now should
copy over the contents of sda1 to sdb1 using dd. In effect you are doing
RAID manually! But this only needs to be done whenever you compile a new
kernel.
--
AJS
delta echo bravo six four at earthshod dot co dot uk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nvidia 7174 + 2.6.12 kernel problem (sid)
Hi again, > If you want you can try my nvidia-update: > http://v0n0.altervista.org/ Thanks one more time. With it, the DVI output is now working. :-) Have a nice day. Olivier -- Olivier Bornet|français : http://puck.ch/f Swiss Ice Hockey Results |english : http://puck.ch/e http://puck.ch/ |deutsch : http://puck.ch/g [EMAIL PROTECTED]|italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/ signature.asc Description: Digital signature
Re: 32bit emu packs
Hi all, On Sat, Nov 05, 2005 at 02:17:18AM +0100, v0n0 wrote: > Hi, I've "repacked" some 32bit libraries for Debian amd64 system, and > Skype and Wine. Skype is running fine, Wine executes, but gives (me) > error on some folders. These are very experimental, but since they don't > mess system, you may want to give it a try! ;) > More infos at: > http://v0n0.altervista.org/ Thanks for it. Skype seems to be working as expected here too. Thanks. Have a nice day. Olivier -- Olivier Bornet|français : http://puck.ch/f Swiss Ice Hockey Results |english : http://puck.ch/e http://puck.ch/ |deutsch : http://puck.ch/g [EMAIL PROTECTED]|italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/ signature.asc Description: Digital signature
