Re: Bug#1081515: gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: Failed to open display
Control: retitle -1 gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: Failed to open display Control: severity -1 serious (Please remove -ports from cc in replies, this is no longer believed to be -ports specific) On Thu, 12 Sep 2024 at 11:48:21 +0100, Simon McVittie wrote: > gtk4's test suite is failing on all -ports architectures that have buildds > > (/<>/debian/build/deb/testsuite/gtk/spinbutton:12693): > Gtk-WARNING **: 17:54:18.469: Failed to open display It seems that it's now also failing on release architectures, and the failure seems well-correlated with weston being upgraded to version 14. The reason this particularly affected -ports is that -ports didn't have an installable version of weston 13, so by definition all of their recent gtk4 builds had to be with weston 14. My current working theory is either a behaviour change in Weston 14, or Weston 14 is crashing part way through testing and all subsequent tests fail. smcv
Bug#1081515: gtk4: FTBFS on -ports architectures: many tests fail with --setup=wayland: Failed to open display
Source: gtk4 Version: 4.14.4+ds-8 Severity: important Tags: ftbfs help X-Debbugs-Cc: debian-po...@lists.debian.org Until recently, gtk4 was not buildable on any -ports architectures because its build-dependency, weston, was uninstallable. Now it's installable, and building and testing can be attempted. gtk4's test suite is failing on all -ports architectures that have buildds, except for m68k (which I believe builds with nocheck and therefore does not run the test suite at all). The GNOME team is busy with GNOME 47 on release architectures and unlikely to have time to look into this in detail any time soon, but if porting teams would like to have GTK 4 available (it will be increasingly important for desktop architectures in trixie), it would be useful if someone from -ports could investigate. The gtk4 test suite is run in two phases: 1. with --setup=x11, wrapped by "debian/tests/run-with-display x11" which is basically xvfb-run 2. with --setup=wayland, wrapped by "debian/tests/run-with-display wayland" which is intended to be a Wayland equivalent of xvfb-run, using weston in headless mode as the compositor Taking powerpc as my arbitrary example, most tests are passing during the x11 phase. On powerpc, I see a failure in "gtk:gtk / sorter" (unstable and experimental) and in "gtk:gdk / memorytexture" (experimental only) which can be investigated separately; please treat those isolated failures as out-of-scope for the purposes of this bug. However, in the wayland phase, most tests are failing with (fatal) warnings like: (/<>/debian/build/deb/testsuite/gtk/spinbutton:12693): Gtk-WARNING **: 17:54:18.469: Failed to open display weston might be broken on all -ports architectures and functional on all release architectures, but that level of coincidence seems a little far-fetched. So my next theory for this is that something is consistently different about the -ports buildds - perhaps their XDG_RUNTIME_DIR is set up differently? - and that is causing "debian/tests/run-with-display wayland" (or the copy of weston that it runs) to fail? After the failure mode discussed in this bug report has been addressed, it will become more useful to look at individual/isolated test failures (as separate bug reports, please). Based on the status of the less-production-ready release architectures like mips64el and riscv64, I suspect that the most common root cause for individual test failures will be the software OpenGL stack: implementation issues in Mesa's llvmpipe and softpipe, implementation issues in LLVM's old MCJIT and new ORCJIT, and the GTK packaging's choice of whether to mitigate llvmpipe bugs by forcing softpipe (currently done on mips*, riscv*, powerpc, sparc*) or test with llvmpipe (as we do on x86, ARM, etc.). Thanks, smcv
Bug#1058740: gtk4,librsvg: big-endian support is at risk of being removed
Source: gtk4,librsvg Severity: important Tags: upstream help X-Debbugs-Cc: debian-s...@lists.debian.org, debian-po...@lists.debian.org gtk4 had a recent test failure regression on s390x and other big-endian architectures like ppc64 (#1057782). I sent this upstream to https://gitlab.gnome.org/GNOME/gtk/-/issues/6260 and proposed a patch in https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6653, but upstream is reluctant to apply the patch because they think it is the wrong solution: > I would rather people fix the actual issue, which is the large table > mapping GdkMemoryFormat to the corresponding GL format (and I bet the > one for dmabufs is broken, too, but we don't have tests for that). librsvg also has long-standing unsolved endianness-related issues, most likely in one of its dependencies (#1038447, which has affected bookworm since September 2022). The GNOME team does not have big-endian hardware where we can run manual tests, so we do not know how much of an impact this has on practical usability of GTK and librsvg on big-endian architectures: it's entirely possible that they have always been misrendered or broken on big-endian, but the bug was never reported because there were no users, and we are only noticing this now as a result of wider test coverage being introduced. If porters are interested in having GTK and librsvg continue to be available on big-endian, please work with upstream to get them to a point where endianness-specific bugs can be taken seriously in the upstream projects. I do not consider doing this downstream-only to be a solution. If endianness-specific issues become a blocker for the Debian release process at some point in the future, then it is likely that I will have to start the process of doing architecture-specific removals for these packages and their reverse dependencies. For s390x this is likely to have little user-visible effect, because I find it unlikely that there are genuinely users running GUI applications on IBM mainframes, but for -ports architectures this will probably be a larger regression. Thanks, smcv
Re: RAID1 all bootable
Yes, looks as if the grub configuration used for the grub-install was not correct (which is definitely if you don't chroot into your mounted HDD with /boot/ being avaiable) On 6 March 2013 21:03, Lennart Sorensen wrote: > On Wed, Mar 06, 2013 at 08:03:12PM +0100, Francesco Pietra wrote: > > Sorry, I forgot both the list and the appropriate output; > > > > root@:/home/francesco# fdisk -l > > > > Disk /dev/sda: 500.1 GB, 500107862016 bytes > > 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x000f1911 > > > >Device Boot Start End Blocks Id System > > /dev/sda1 *2048 385023 191488 fd Linux raid > autodetect > > /dev/sda2 385024 976166911 487890944 fd Linux raid > autodetect > > > > Disk /dev/sdb: 500.1 GB, 500107862016 bytes > > 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0xcca6 > > > >Device Boot Start End Blocks Id System > > /dev/sdb1 *2048 385023 191488 fd Linux raid > autodetect > > /dev/sdb2 385024 976166911 487890944 fd Linux raid > autodetect > > OK, so that is the normal setup with partitions. grub-install /dev/sda > and /dev/sdb should have worked fine (but of course it has to be run > from the system, not some other thing like knoppix or the like) or from > a chroot into the system even if booted from something else. > > > Disk /dev/md0: 195 MB, 195887104 bytes > > 2 heads, 4 sectors/track, 47824 cylinders, total 382592 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/md0 doesn't contain a valid partition table > > > > Disk /dev/md1: 499.5 GB, 499465912320 bytes > > 2 heads, 4 sectors/track, 121939920 cylinders, total 975519360 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/md1 doesn't contain a valid partition table > > > > Disk /dev/mapper/vg1-root: 998 MB, 998244352 bytes > > 255 heads, 63 sectors/track, 121 cylinders, total 1949696 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/mapper/vg1-root doesn't contain a valid partition table > > > > Disk /dev/mapper/vg1-swap: 15.0 GB, 14998831104 bytes > > 255 heads, 63 sectors/track, 1823 cylinders, total 29294592 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/mapper/vg1-swap doesn't contain a valid partition table > > > > Disk /dev/mapper/vg1-usr: 30.0 GB, 29997662208 bytes > > 255 heads, 63 sectors/track, 3647 cylinders, total 58589184 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/mapper/vg1-usr doesn't contain a valid partition table > > > > Disk /dev/mapper/vg1-opt: MB, 220736 bytes > > 255 heads, 63 sectors/track, 1215 cylinders, total 19529728 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/mapper/vg1-opt doesn't contain a valid partition table > > > > Disk /dev/mapper/vg1-var: MB, 220736 bytes > > 255 heads, 63 sectors/track, 1215 cylinders, total 19529728 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/mapper/vg1-var doesn't contain a valid partition table > > > > Disk /dev/mapper/vg1-tmp: 2998 MB, 2998927360 bytes > > 255 heads, 63 sectors/track, 364 cylinders, total 5857280 sectors > > Units = sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 4096 bytes > > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > > Disk identifier: 0x > > > > Disk /dev/mapper/vg1-tmp doesn't contain a valid partition table > > > > Disk /dev/mapper/vg1-home: 430.0 GB, 43046080 bytes > > 255 heads, 63 sectors/trac
Re: RAID1 all bootable
Hi Francesco, I was under the impression your grub configuration was correct and the only thing wrong was not having it installed on that one HDD. Of course your grub configuration should point to the correct root. In my little (easy) setup I have my main partition, boot partition and swap partition in raid-1. The update-grub command was able to create the correct entries for this configuration in my grub.cfg all by itself. If grub is sending you to the rescue prompt it means something it wrong with your grub configuration, so you'll have to fix that and install grub again. With kind regards, Simon On Mar 3, 2013 8:48 AM, "Francesco Pietra" wrote: > Hi Lennart, Hi Simon > > A proper understanding of mdadm is required. Hurrying with focus on > codes for biochemical applications has brought me into a mess. > > Relying of all my data, and special compiled programs, present on > another raid1 amd64 wheezy, I carried out a reinstall of amd64 wheezy > on the machine with new HD. mdo (boot, ext20, md1 (LVM, home, usr, > etc). GRUB was installed on /dev/sda > > Then the command > > grub-install /dev/sdb > with reported installation compete. No errors reported. > > On rebooting, GRUB was no more found, entering in > > grub rescue > > > which should also be known accurately, because prefix/root/ are now wrong. > > > The only care I exerted, was not to work with the machine where I have > my data, until the damaged machine is in order again. At any event, > how to install safely GRUB on both disks of a RAID1 is a must. > > Thanks for your kind advice. > > francesco pietra > > As to mdadm, > > On Sat, Mar 2, 2013 at 7:05 AM, Simon Vos wrote: > > Have you assembled you raid devices again (mdadm --assemble /dev/mdX > > /dev/sdX)? > > > > That should still work with the disk that was used for your RAID-1, when > > that's done you can mount your disk, chroot into it and run grub-install > > /dev/sda (and grub-install /dev/sdb, so you won't have this problem in > the > > future ;-)). > > > > > > On 2 March 2013 11:10, Francesco Pietra wrote: > >> > >> A further piece on information. With knoppix 7.0, the procedure for > >> examining mdadm arrives at > >> > >> cat /proc/partitions > >> sda > >> sdb > >> > >> RAID1 (md0 md1) is not seen. I assume that this is the way Knoppix > >> behaves in this situation. > >> > >> Thanks > >> francesco pietra > >> > >> > >> -- Forwarded message -- > >> From: Francesco Pietra > >> Date: Sat, Mar 2, 2013 at 10:11 AM > >> Subject: Re: RAID1 all bootable > >> To: Lennart Sorensen , amd64 Debian > >> , debian-users > >> > >> > >> > >> Is this recipe devised for installing grub on both sda and sda with an > >> undamaged RAID1? > >> > >> In my case, with the sda that contained grub loader replaced by a new > >> disk, the rescue mode (using the same CD installer for amd64 wheezy) > >> did not find any partition. Inverting the SATA cables, same result. > >> > >> In both cases (I mean position of SATA cables) I went to the shell in > >> the installer environment: > >> > >> #fisk /dev/sda (or sdb) > >> device contains neither a valid DOS partition table, nor Sun, etc > >> (expected for a raid) > >> > >> #dmesg |grep -i sd > >> sda (and sbb): unknown partition table (expected for a raid), however > >> md: raid0 > >> md: raid1 > >> were identified, along with rai4, 5, 6 etc (unfortunately "| less" > >> does not work to see the whole message). > >> > >> Am I using the Rescue Mode improperly? I was unable to dig into the HD > >> that contains md0 (booth loader, EXT2) and md1 ( LVM partitions home > >> tmp usr opt var swap EXT3) > >> > >> Thanks a lot for your kind advice > >> > >> francesco pietra > >> > >> > >> > >> On Fri, Mar 1, 2013 at 10:35 PM, Lennart Sorensen > >> wrote: > >> > On Fri, Mar 01, 2013 at 08:20:09PM +0100, Francesco Pietra wrote: > >> >> Hi: > >> >> With a raid1 amd64 wheezy, one of the two HDs got broken. > >> >> Unfortunately, I had added grub to sda only, which is just the one > >> >> broken. So that, when it is replaced with a fresh HD, the OS is not > >> >> found. Inverting the SATA cables of course does not help (Operative > >> >> System Not Fou
Re: RAID1 all bootable
Have you assembled you raid devices again (mdadm --assemble /dev/mdX /dev/sdX)? That should still work with the disk that was used for your RAID-1, when that's done you can mount your disk, chroot into it and run grub-install /dev/sda (and grub-install /dev/sdb, so you won't have this problem in the future ;-)). On 2 March 2013 11:10, Francesco Pietra wrote: > A further piece on information. With knoppix 7.0, the procedure for > examining mdadm arrives at > > cat /proc/partitions > sda > sdb > > RAID1 (md0 md1) is not seen. I assume that this is the way Knoppix > behaves in this situation. > > Thanks > francesco pietra > > > -- Forwarded message -- > From: Francesco Pietra > Date: Sat, Mar 2, 2013 at 10:11 AM > Subject: Re: RAID1 all bootable > To: Lennart Sorensen , amd64 Debian > , debian-users > > > > Is this recipe devised for installing grub on both sda and sda with an > undamaged RAID1? > > In my case, with the sda that contained grub loader replaced by a new > disk, the rescue mode (using the same CD installer for amd64 wheezy) > did not find any partition. Inverting the SATA cables, same result. > > In both cases (I mean position of SATA cables) I went to the shell in > the installer environment: > > #fisk /dev/sda (or sdb) > device contains neither a valid DOS partition table, nor Sun, etc > (expected for a raid) > > #dmesg |grep -i sd > sda (and sbb): unknown partition table (expected for a raid), however > md: raid0 > md: raid1 > were identified, along with rai4, 5, 6 etc (unfortunately "| less" > does not work to see the whole message). > > Am I using the Rescue Mode improperly? I was unable to dig into the HD > that contains md0 (booth loader, EXT2) and md1 ( LVM partitions home > tmp usr opt var swap EXT3) > > Thanks a lot for your kind advice > > francesco pietra > > > > On Fri, Mar 1, 2013 at 10:35 PM, Lennart Sorensen > wrote: > > On Fri, Mar 01, 2013 at 08:20:09PM +0100, Francesco Pietra wrote: > >> Hi: > >> With a raid1 amd64 wheezy, one of the two HDs got broken. > >> Unfortunately, I had added grub to sda only, which is just the one > >> broken. So that, when it is replaced with a fresh HD, the OS is not > >> found. Inverting the SATA cables of course does not help (Operative > >> System Not Found). In a previous similar circumstance, I was lucky > >> that the broken HD was the one without gru. > >> > >> Is any way to recover? perhaps through Knoppix? I know how to look > >> into undamaged RAID1 with Knoppix. > >> > >> Also, when making a fresh RAID1 from scratch, where to find a Debian > >> description of how to make both sda and sdb bootable? (which should > >> be included by default, in my opinion) > > > > You can boot the install disk in rescue mode, select the root partition > > to chroot into, then run grub-install from there. > > > > When grub asks where to install, you should configure it for both sda > > and sdb. I think 'dpkg-reconfigure grub-pc' is where that is selected. > > Might need it to use -plow to asks all levels of questions. Not sure. > > > > -- > > Len Sorensen > > > -- > To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/caev0nmtmhadi2e_uk+wf+c0k9d1ygn3tv91jsr4g2ppp5_a...@mail.gmail.com > >
Re: [SPAM detected Spam-Test: True ; 4.0 / 3.0] Re: Re: Grub-pc problem
Sorry, I have been able to solve the problem in the mean time. For some reason one of the grub commands called by the script that creates grub.cfg failed. It was the one retrieving the id of the HDD. I changed the grub.cfg file manually to use a /dev/ device instead of uuid and my laptop booted again. After that I tried running the script manually after updating my system again and everything worked again. And I was using grub2 already, I was *not* booting grub2 through grub1.. Simon On Fri, Oct 23, 2009 at 5:47 PM, naths wrote: > Hi Simon, > > After upgrading you may have option for grub legacy or grub2 for use. > Please check which one you are using.You have to use command > 'upgrade-from-grub-legacy' to use grub2 permanently. > > grub2 use file /boot/grub/grub.cfg and legacy file /boot/grub/menu.lst > compare to use right device for root. > > /usr/share/doc/grub* may help you. > > Have fun > > regards, > > G.NATH > > > > -- > To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > >
Re: Grub-pc problem
Thank you for the suggestions, I will try to look at the configuration and see if that is the problem. I am not upgrading from grub-legacy, I have been using grub-pc for some time now. I tried to downgrade to the previous version or grub-pc, but that didn't work for me either. On Oct 7, 2009 1:24 AM, "Michael" wrote: >Try 'search' (search devices by a file or a filesystem label) and 'help'. oh if you're still on legacy then it's rather 'find' not 'search' -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe"...
Grub-pc problem
Hello, I have an AMD64 debian unstable installation running on my laptop. I upgraded my system today, but while installing an updated version of grub-pc something goes wrong. It tells me that it "cannot find a device for /boot/grub" while executing grub-probe. What can I do to try and solve this issue on my pc (or perhaps work around this)? Simon
Re: What is the best java for debian-amd64 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The java-6-openjdk is the one I use. It is the completely open version of the JDK released by sun under the GPL. In fact it is IcedTea, which is a project created to have a complete open JDK. The source release by Sun was not complete, since some parts of their source were not their intelectual property. For these parts of the source Sun added binaries, the IcedTea project re-implemented the non-open parts. For as far as I have used the java-6-openjdk it seems to me that it is complete. I think I read online that IcedTea had passed the TCK (the java compatibility test) and it is completely open-source. Also, it is the default default java alternative in debian I think.. With kind regards, Simon Hans-J. Ullrich wrote: > Hi all, > > as there are many java versions installable, what is the best one to use in > amd64-systems ? What are the differences ? I saw gcj, gij, gdk, java. Can > someone tell me, which should be used ? Ia ma very confused. > Update-alternatives is giving me these choices: > > There are 8 alternatives which provide `java'. > > SelectionAlternative > --- > 1/usr/bin/gij-4.1 > 2/usr/lib/jvm/ia32-java-6-sun/jre/bin/java > 3/usr/lib/jvm/java-gcj/jre/bin/java > 4/usr/bin/gij-4.3 > * 5/usr/lib/jvm/java-6-sun/jre/bin/java > 6/usr/bin/gij-4.2 > 7/usr/lib/jvm/ia32-java-1.5.0-sun/jre/bin/java > +8/usr/lib/jvm/java-6-openjdk/jre/bin/java > > Press enter to keep the default[*], or type selection number: > > I choose 5. What is this "+"-sign meaning ? > > Questions, questions, questions > > Thanks for any help ! > > > Kind regards > > Hans-J. Ullrich > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjSj4cACgkQbAyTrjLX2Rm+GQCcDPHPzE+xN/mEW8DwbA82k8sY 7bIAnA+8LUZ3jT9zfWZBXTypSdDXFNEu =b5AZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dvi vs vga etc and monitors.....
On 28 May 2008, at 8:17 AM, Michael Fothergill wrote: Is it really true that if you had a very long 50 meter vga cable the signal would degrade and you would lousy graphics resolution in the monitor relative to a short 2 meter vga lead between computer and monitor? The quality of the VGA cable will certainly effect the quality of the image, the cheap ones can look awful at any length. 50 meters is asking quite a lot of the graphics card, and is outside the specs for VGA (you really should get an amplifier for the VGA signal for long runs - with good cables this works well), but it can work - depending on the card, the cable and the monitor. Is it also true that if you switched it for a 50 meter DVI cable then everything would be perfect and the signal degradation would vanish? for long runs VGA is better, DVI doesn't work for long runs, although there are some (very expensive) longer DVI cables around, I think the maximum is much less than 50 meters. Using a multicore cable with 5x video cables and an appropriate adapter to VGA will also work well (they are usually much better than VGA cables for long runs), but none of the other communication between monitor and graphics card will work so everything will need to be set manually. Note that you must use a multicore cable as the signal paths for the 5 connections need to be identical. When using projectors scattered around a big venue I usually try to put the playback computers near the projectors and control them via ethernet. simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem with avahi-daemon
Hello, I have an annoying problem with avahi-daemon. When the init-Script starts I receive the message: Starting Avahi mDNS/DNS-SD Daemon: avahi-daemonTimeout reached while wating for return value Could not receive return value from daemon process. failed! Does anybody else have this problem too? Or has anybody an idea about this issue? BTW: I tried other versions (lenny and etch) of avahi-daemon and its all the same. Regards Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nvidia way versus debian way of installing nvidia 3D graphics drivers in Lenny..
The wiki is not out of date at all. By the way, this way of installing the nvidia drivers has been around for some years now. I use module-assistant in sid and it has worked fine for me from the first moment I used it. Before that I used make-kpkg, this worked too, but the module-assistant takes away a lot of work. Michael Fothergill wrote: > Dear Debianists, > > I have installed Debian Lenny on my HP G6062 laptop. Xserver works > reasonably using the vesa driver. I couldn't get it to work with the nv > driver. > > It seems to see the nvidia network controller as well. > > There is an nvidia 7000M graphics chip in the laptop. I assume that it could > do some 3D graphics processing. > > But if I would want to use this capability I would need to install the > proprietary nvidia drivers manually. > > I Googled this and found quite a few web pages on this. > > It seems that Nvidia have their own installer and guide on their own web site > for Linux users but Debian also has its own Debian Way of installing the > nvidia drivers. > > There also seems to be other individuals with web pages giving advice on this > subject. > > Left to my own devices I would likely choose this site to get instructions on > how to proceed here: > > http://wiki.debian.org/NvidiaGraphicsDrivers > > But this seems to be a fast moving subject and maybe this site is out of date > now. > > I would appreciate comments on which web sites provide the most up to date > and appropriate way of doing it. > > I will use those sites and ignore the other ones and install the drivers. > > Regards > > Michael Fothergill > > > > > > > > > > > > _ > Win 100’s of Virgin Experience days with BigSnapSearch.com > http://www.bigsnapsearch.com > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Compiz window decoration
Hello everyone, I have a little problem with the compiz windowmanager in gnome, The window decoration is not visible, or sometimes its glitched, but only when the window is not the active window. Is there anyone else with this problem? At first I thought it would be a little bug in compiz, but I haven't seen a change in this, so it might just be me. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Video playback using xv driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Today I tried to playback a video on my pc using totem, but the colors were wrong. The faces of the people in the video were blue-ish. This problem occurs with totem, but also with vlc and mplayer, so I thought maybe its the outpu that is wrong, so I tried x11 instead of xv in mplayer and vlc and this worked. Does anyone have the same problem with their nvidia graphics card using the "nvidia" xorg driver? Regards, Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH7PNObAyTrjLX2RkRAjjFAJ0dDjrfhSDW8hrExKQjEq43uSBrWACgth09 5Q7kH5pkifLxzSYEcjO//H0= =RTGn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
*fixed* Re: dead link on /ports/amd64
On Wed, Feb 27, 2008 at 10:40:37AM +0100, Simon Paillard wrote: > ~/debian/webwml$ rgrep -l > 'http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/?cvsroot=debian-amd64' * >[..] > > I guess that the proper URL should be : > > http://alioth.debian.org/plugins/scmcvs/cvsweb.php/?cvsroot=debian-amd64 Fixed in the CVS. -- Simon Paillard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dead link on /ports/amd64
[ CC'ing debian-amd64 ] On Wed, Feb 27, 2008 at 09:12:10AM +0100, Franklin PIAT wrote: > On Wed, 2008-02-27 at 08:33 +0100, Franklin PIAT wrote: > > On Tue, 2008-02-26 at 22:08 -0800, Sarit Ritwirune wrote: > > > http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/?cvsroot=debian-amd64 > > > > Can you tell us where you fount the URL. > > Was it on http://www.debian.org/ports/amd64 or somewhere else ? > > I've yahoo'd and gogoled a bit. It reported no other occurrence, except > on http://wiki.debian.org/DebianAMD64 It's sure there is no other occurence : ~/debian/webwml$ rgrep -l 'http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/?cvsroot=debian-amd64' * danish/ports/amd64/index.wml [.. other languages .. ] spanish/ports/amd64/index.wml > I guess that the proper URL should be : > http://alioth.debian.org/plugins/scmcvs/cvsweb.php/?cvsroot=debian-amd64 CC'ing debian-amd64, do you confirm ? do you want to refresh something else on the http://www.debian.org/ports/amd64 page ? Regards -- Simon Paillard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Etch amd64 mirror
Hello Alexander, On Wed, Dec 26, 2007 at 02:10:01PM +0200, Alexander Golovin wrote: > When I use the Primary Debian mirrors sites for creating Etch amd64 > Debian local ftp mirror with debmirror, in it a case I receive error: > some files is missing on Primary mirror site. That is a know problem in the archive maintenance scripts themselves already reported many times : See bugs 439084 443337 23 448778 455089 on ftp.debian.org pseudopackage http://bugs.debian.org/23 for example PS: there is no need to flood so many lists... -- Simon Paillard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Plugins
Am Donnerstag, den 03.05.2007, 23:05 -0500 schrieb Pepo: > Hi friends. > > Please, How do I can use plugins in Iceweasel if I am using Lenny-AMD64? > (java, flash player) > > Thanks. On sid-amd64 there is nspluginwrapper. With that little piece of software you can run the Adobe Flash-Player on amd64. If you don´t want to mix up your system with unstable you can get nspluginwrapper from http://gwenole.beauchesne.info/projects/nspluginwrapper/ You don´t have to compile it. Just take the two *.rpm files (both Plugin _and_ Viewer), convert them with alien into deb and install. Normally this should work. More instructions you can find on the Web-Site mentioned above. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PovRAY - Where are you?
I can remember using PovRAY to do benchmark testing back just before the AMD64 port became part of the regular Debian platform set. Anyone know why it isn't available now. for licensing reasons (it's license is too restrictive for Debian 'main') it's in 'non-free' rather than 'main' simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: flash...
libflash-mozplugin ? - Original Message From: sigi <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Sent: Sunday, November 12, 2006 9:05:59 PM Subject: flash... Hi, I know, that there is no real flashplayer for amd64 out there... but some times ago I had a library installed, that displayed simple flash-pages on the web - but I forgot it's name, and found nothing via google anymore... I think, I got it's name here on this list. It was not gnash or swf-player - only one little lib, which I had to install, afaik. Does anybody here now something else besides gnash and swf-player? Thanks for your help, sigi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help: Asrock NF3, aperture from agp bridge too small...
Title: Re: Help: Asrock NF3, aperture from agp bridge too small... Hello, I've got the same problem. I've the same Motherboard. The Distro is Mandriva 2006, x86_64, with 2.6.12 Kernel. Did you solve the problem? Mit freundlichen Grüßen / Best regards Andreas Simon mailto:[EMAIL PROTECTED]
IBM Series x3650 Question
Hi There, Wondering if any one has any info on the new IBM Series x3650 servers running with Debian. In particualr with the upgraded ServeRAID-8k SAS Controller option (25R8064) from IBM? This has full RAID 5 support with battery backup of 72 hours. Im guessing that the only issue with this server would be the raid controller being too new for debian to recognise...? This adaptor is showen as being supported by both RHEL and SLES: http://www-03.ibm.com/servers/eserver/serverproven/compat/us/blade/8853/ibm_25R8064.html And here is the IBM Redbook: http://www.redbooks.ibm.com/abstracts/TIPS0054.html?Open I would really appreciate any input here, esp from anyone from IBM on this list? Thanks Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gnome hangs when clicking 'Desktop' menu
I have debian etch, with gnome installed. I connect via vnc and have 'gnome-session &' in my .vnc/xstartup file. It seems to work fine but hangs when ever I click on 'Desktop' on the menu/panel. All other menu items work as expected, until 'Desktop' is clicked, then everything stops responding. Anyone know why and/or how to fix this? Thanks, Brendan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Recent sid amd64 rpath oddity?
Hi, On the 3rd May I built libxfce4util and generated libxfce4util2_4.3.90.1-1_amd64.deb. This is in the archive exactly as I built it. It has a couple of lintian failures that I missed and have since been fixed in our SVN. Upstream have released recently and whilst checking these packages more thoroughly I've fixed up the lintian errors but I've also built the new package and I noticed that it's defining an rpath. So I rooted around and tried to work out why but couldn't really work it out. Upstream's libtool and autotools looked recent to me. If I relibtoolize though this does go away. Out of curiousity I rebuilt the previous package i.e. 4.3.90.1-1 again from the same source files as before but with current sid and this time it fails with two extra lintian warnings: W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/lib/libxfce4util.so.2.1.0 /usr/lib W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/sbin/xfce4-kiosk-query /usr/lib If I rebuild the same package on i386 current sid then I don't get the rpath installed. I guess I have several questions: - how can the same source package over a few months build differently in this way? - am I really going to have to relibtoolize every xfce package before I upload or make them do it themselves? :-/ - how evil is an rpath on /usr/lib anyway? I'd welcome any testers on amd64 or not and on recent sid or not to narrow this down. Or any clues as to how on earth this can happen. If you do want to relibtoolize then install xfce4-dev-ools and run xdt-autogen in the package dirrectory. Thanks. Simon. heh, good sigmonster. -- oOoOo Open source is about letting go of complete control. Accept oOoOo oOoOo the fact that other people are wonderful resources tooOoOo oOoOo fixing problems, and let them help you. - Linus Torvalds oOoOo htag.pl 0.0.22 ::: http://www.earth.li/~huggie/ signature.asc Description: Digital signature
Re: Server REALLY slow after console messages
Kernel 2.6.8-12-em64t-p4-smp On 6/28/06, Hemlock <[EMAIL PROTECTED]> wrote: On Wed, 28 Jun 2006 09:07:02 +1200, Simon wrote > Hi There, > > Can anyone have a look at this screenshot and give me a glimmer of > what is going on here? > > This server is responding to pings, but all services are 'stuck', i > can login, but it times out after 60 seconds and typing is REALLY > slow... > > http://gremin.orcon.net.nz/mx.JPG > > Thanks for any input Running a 2.6.15 kernel? -- 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]
Re: Server REALLY slow after console messages
On 6/28/06, Jo Shields <[EMAIL PROTECTED]> wrote: You've run out of RAM. Hmm... Could this be some sort of memory leak or something? Would anyone be able to offer any path of checking or solving this issue? Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Server REALLY slow after console messages
Hi There, Can anyone have a look at this screenshot and give me a glimmer of what is going on here? This server is responding to pings, but all services are 'stuck', i can login, but it times out after 60 seconds and typing is REALLY slow... http://gremin.orcon.net.nz/mx.JPG Thanks for any input Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Optimum kernel for Xeon with em64t
Thanks for the reply Jo... another question if i could please: On 6/12/06, Jo Shields <[EMAIL PROTECTED]> wrote: No, you're not running the right kernel - 2.6.8-9 is very old, and has security flaws in it. If you stick with sarge, update your kernel to kernel-image-2.6.8-12-em64t-p4-smp - or more generally, install the kernel-image-2.6-em64t-p4-smp metapackage Cool, so the meta package always depends on the latest kernel image, nice. Should there be any worry in installing this updated kernel on my server? The only complied software is amavis-new... other than that its all apt-get'ed. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Optimum kernel for Xeon with em64t
Hi There, I have a dual processor server with 2 x 2.8GHz processors which supports EM64T. Currently i am running kernel 2.6.8-9-em64t-p4-smp and a "cat /proc/cpuinfo" shows 4 processors (the 2 hyperthreaded processors). My question is: What is the optimum kernel to be running for my setup? Am i running the correct one? This is a mail server that has debian sarge installed and runs dbmail/amavis/postfix and supplies incoming and outgoing mail for our clients - is there even a reason here to run a EM64T kernel in this case? Thanks Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Sarge server frozen (em64t-p4-smp)
On 4/6/06, Stephen Woodbridge <[EMAIL PROTECTED]> wrote: > Simon, > > Have you checked your 3ware logs, are you getting any disk errors? Which > controller are you running? Have you run fsck on all the partitions? Not > sure any of these will help as Lennart said, it does sound like > something hardware is start to fail. > > -Steve > > Lennart Sorensen wrote: > > On Wed, Apr 05, 2006 at 07:02:48PM +1200, Simon wrote: > > > >>Hi There, We have a mail server (postfix>amavis>dbmail) running debian > >>sarge (2.6.8-9-em64t-p4-smp) running dual xeons with a tyan > >>motherboard and 3ware hardware raid5. Everything has been running fine > >>up to now, but in the last week it has frozen twice. Completly stuck > >>needing a hard reboot to restart (ctl-alt-del dosnt work). Here is a > >>screenshot of the stuck screen (no ping, nothing at this point): > >> > >>http://gremin.orcon.net.nz/console.jpg > >> > >>Would someone be able to take a look and give me a clue here? > > > > > > I wonder what autoremove_wake_function is... > > > > journal_commit_transaction looks related to one of the journaling > > filesystems, specifically ext3 I believe. > > > > Can you do a shift+pgup to see more of the output? How about setting up > > a serial console or remote logging so you can capture the full error > > messages? > > > > Of course it really sounds like either you upgraded something recently > > that is broken, or the hardware is starting to fail. We did have a disk spit itself out of the 3ware hw raid a couple of weeks ago, the spare kicked in and was all OK. After a re-start all seemed fine again... but now seems like too much of a coincidence to ignore. Replace the drive?? - im guessing yes :) Unfort i cant scroll up as the box was really suck.. nothing but a hw reset worked. Simon
Debian Sarge server frozen (em64t-p4-smp)
Hi There, We have a mail server (postfix>amavis>dbmail) running debian sarge (2.6.8-9-em64t-p4-smp) running dual xeons with a tyan motherboard and 3ware hardware raid5. Everything has been running fine up to now, but in the last week it has frozen twice. Completly stuck needing a hard reboot to restart (ctl-alt-del dosnt work). Here is a screenshot of the stuck screen (no ping, nothing at this point): http://gremin.orcon.net.nz/console.jpg Would someone be able to take a look and give me a clue here? Simon
Simon
Good afternoon, Burke See you Burke Burke Burke Burke Burke Burke Burke Burke Burke Burke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Troubles installing Debian on an ASUS notebook
I've experienced problems with a couple of devices which freeze on the default linux2.4 boot on the net install cd. Have you tried entering 'linux26' at the boot: prompt? Simon Mike wrote .. > Sound's like a media problem to me. I'd try checking the md5 sums on the > disk (you have to burn disk-at-once), preferably on the laptop. I'm not > sure if debian install comes with a checking. You could also try booting > from a usb jump drive, not sure what options are available. I know my > dell > laptop has a very very picky dvd drive, especially for cdroms. Though > I > expect your Asus to be much better than my dell :-) > > > > - Original Message - > From: "Lennart Sorensen" <[EMAIL PROTECTED]> > To: "Emmanuel Guiton" <[EMAIL PROTECTED]> > Cc: > Sent: Thursday, October 13, 2005 10:03 AM > Subject: Re: Troubles installing Debian on an ASUS notebook > > > > On Thu, Oct 13, 2005 at 12:50:32PM +0200, Emmanuel Guiton wrote: > >> For 2 days, I've been trying to install in vain Debian on my ASUS A6QK30 > >> (AMD Turion 64 processor). > >> Is there anyone who has successfully done a 64 bit installation on that > >> kind of notebooks? > >> > >> I tried these methods: > >> - installing from the sarge netinst CD: it kind of freezes right after > >> the country selection > >> - installing from the sarge CDs: same problem > >> - installing from the etch netinst CD: I got the following error: > >> ISOLINUX 2.04 2003-04-16 Copyright (C) 1994-2003 H. Peter Anvin > >> Could not find kernel image: linux > >> boot: _ > >> > >> md5 checksums of the downloads were alright. > >> > >> Does anyone have a clue on how should I proceed? > > > > What chipset, video, etc does that machine use? > > > > Does the i386 sarge installer work on it? > > > > Len Sorensen > > > > > > -- > > 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] > > >
Re: Mozilla Thunderbird bug?
Hi I'm using Thunderbird 1.0.2 right now on kernel 2.6.8-11-amd64-generic and it saves outgoing messages just fine. I too am using Cyrus-imap onto another Debian server which is the mail host. If there is a known bug, it doesn't seem to affect me. For the record, I migrated the profile (ftp!) from a Windows XP host and it worked "out of the box". Regards Simon Alex Ferrara wrote: My PC used to run i386 Debian, and I have recently moved over to AMD64 port. I have noticed that Mozilla Thunderbird does not want to save a copy of an outgoing message to my Sent folder. I had the same config under i386 Debian using the same mail server (Cyrus-imap), and all was well. After much searching, I have found that this is not a new bug, but has been around for quite a while. I found that playing with the advanced settings in Thunderbird allowed me to save items in sent, but it did not see all my other folders in the imap tree. Ideas anyone? aF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: building nvidia drivers
This worked for me: This worked for me for kernel 2.6.8-11-amd64-generic. Good luck Simon == Make sure the following are in /etc/apt/sources.list: deb http://amd64.debian.net/debian-amd64 stable main non-free contrib deb http://amd64.debian.net/debian-amd64 unstable main non-free contrib Make sure you've got all the kernel sources - all these are needed as they have symbolic links in them. $ apt-get install kernel-kbuild-2.6-3 kernel-headers-2.6.8-11-amd64-generic kernel-headers-2.6.8-11 nvidia-kernel-source nvidia-kernel-common Get the module assistant: $ apt-get module-assistant Set up the appropriate kernel sources ready for the module assistant: $ m-a -i prepare Build the kernel module: $ m-a a-i -i -t -f nvidia-kernel Now get the other packages needed for getting the nvidia drivers working: $ apt-get install nvidia-glx nvidia-glx-dev If you haven't got xfree86 installed, install it: $ apt-get install xserver-xfree86 Otherwise, reconfigure it: $ dpkg-reconfigure xserver-xfree86 Select 'nvidia' for the driver when prompted. Enter whatever you want for the card name, and just press 'return' for the Bus Identifier and for amount of RAM. All other options depend on what you want. Best bet is to select 'simple' for the monitor configuration! Dean Hamstead wrote: hi all just did a clean install on my shiny new amd64 before i post mboard specs (im running on a dfi lanparty ut sli-d) can someone shed some light on why i cant built the nvidia drivers i followed the instructions on alioth it didnt work ;) now for some details (as root)... mele:/usr/src/kernel-headers-2.6.8-11-amd64-k8# MAKEFLAGS="CC=gcc-3.4" make-kpkg --append-to-version -11-amd64-k8 modules_image /usr/bin/make EXTRAVERSION=-11-amd64-k8-11-amd64-k8 \ ARCH=x86_64 oldconfig make[1]: Entering directory `/usr/src/kernel-headers-2.6.8-11-amd64-k8' HOSTCC scripts/kconfig/mconf.o scripts/kconfig/mconf.c:91: error: static declaration of 'current_menu' follows non-static declaration scripts/kconfig/lkc.h:63: error: previous declaration of 'current_menu' was here make[2]: *** [scripts/kconfig/mconf.o] Error 1 make[1]: *** [oldconfig] Error 2 make[1]: Leaving directory `/usr/src/kernel-headers-2.6.8-11-amd64-k8' make: *** [stamp-kernel-configure] Error 2 mele:/usr/src/kernel-headers-2.6.8-11-amd64-k8# bummer nothing!! heres my sources.list, im up to date (apt-get update; apt-get upgrade) mele:/usr/src/kernel-headers-2.6.8-11-amd64-k8# cat /etc/apt/sources.list #deb file:///cdrom/ sarge main deb http://public.planetmirror.com/pub/debian-amd64/debian/ unstable main contrib non-free deb http://public.planetmirror.com/pub/debian-amd64/debian/ stable main contrib non-free #deb-src http://debian.csail.mit.edu/debian-amd64/debian/ unstable main contrib non-free deb http://security.debian.org/ stable/updates main mele:/usr/src/kernel-headers-2.6.8-11-amd64-k8# Dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
freeNX in 32-bit chroot
Hi all Having struggled with getting FreeNX running under amd64 (nxagent just core dumps all the time), I decided to try running it in chroot. I've set it up inside my ia32 chroot, but am having difficulty getting it to work outside (via dchroot script). I've set up an nx user to point at the nx user home within the chroot, and I've set up symlinks in /usr/lib/nx to dchroot the equivalent binaries in the chroot (along with a couple more in /usr/bin and /user/sbin). Trouble is, this all seems a bit of a hack way of doing it. When I connect with the nxclient, it fails with the log: NX> 203 NXSSH running with pid: 3780 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 200 Connected to address: 192.168.1.15 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey dchroot: chdir: No such file or directory No shell ...so I guess I have missed a link somewhere. I seem to remember reading that someone had done this? Alternatively, if anyone has managed to get FreeNX working under amd64 natively, that would be great too. Thanks Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian SID AMD64 kernel 2.6.12
Hello everyone, I have a problem with the kernel configuration. While trying to configure the kernel I'm missing two drivers for my two nic's. I have a realtek 8139 nic and the nic on board of my nforce 2 motherboard. I've just installed the AMD64 port of debian and I can't find the configuration options for these nic's. In the i386 port I didn't have this problem. Simon
Xen on amd64
I noticed there's an unstable release of Xen on xensource.org for amd64. Has anyone tried this? I have an amd64 box I want to use as a dev system, running 64-bit Debian, but I need to develop a small custom distro for a thin client system. I thought maybe I could install Xen and then put AMD64 Debian and a 32-bit-something-else on it. Simon
Re: dpkg-architecture issues/vmware
I did have 1.10.28 from sarge, but I upgraded gcc to build a package earlier. I will change the link to point to the right one. I got dpkg from amd64.debian.net unstable, I think. But I may be wrong. Thanks for your help. Also - forgive the newbie question - but can someone tell me how to 'downgrade' a package? Is it a matter of removing it completely then picking the right apt source to install from? Simon Kurt Roeckx wrote .. > On Fri, Aug 26, 2005 at 12:35:07AM +0100, Simon Guerrero wrote: > > Hi > > > > Around the same time, I noticed something odd about dpkg. > > dpkg-architecture (at version 1.13.1.11 of dpkg) gives: > > Where did you get that version of dpkg? In sarge it's 1.10.28 in > sid it's 1.13.11 and in etch is should be 1.13.10. > > > dpkg-architecture > > dpkg-architecture: warning: Unknown gcc system type x86_64-linux-gnu, > > falling back to default (native compilation) > > dpkg-architecture: warning: Specified GNU system type x86_64-linux does > > not match gcc system type x86_64-linux-gnu. > > This means your gcc and dpkg do not have a version that go > together. > > > Kurt > > >
dpkg-architecture issues/vmware
Hi I've managed to get nvidia drivers and madwifi working on my amd64 box, but something's gone wrong while I've been installing vmware 30-day demo. I can't get the bridged networking to work, and I've tried a couple of the vmware-any-any patches. Around the same time, I noticed something odd about dpkg. dpkg-architecture (at version 1.13.1.11 of dpkg) gives: dpkg-architecture dpkg-architecture: warning: Unknown gcc system type x86_64-linux-gnu, falling back to default (native compilation) dpkg-architecture: warning: Specified GNU system type x86_64-linux does not match gcc system type x86_64-linux-gnu. DEB_BUILD_ARCH=amd64 DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_GNU_SYSTEM=linux DEB_BUILD_GNU_TYPE=x86_64-linux DEB_HOST_ARCH=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_HOST_GNU_SYSTEM=linux DEB_HOST_GNU_TYPE=x86_64-linux uname -r gives: 2.6.8-11-amd64-generic Can anyone give me any pointers here? I changed my sources.list back and forward quite a lot when installing the nvidia and madwifi stuff and I figured maybe I had messed up the version of something significant. Thanks Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
running ie6 using wine under amd64
Hi I'm sure this has been asked before - and there are many HOWTOs - but I just can't get it to work. To pre-empt the obvious questions: I want to do this because I'm doing some development of a device which is linux-based but can run ie6 locally along with RDP. Unfortunately my main linux dev box is amd64, which complicates matters. I think I've installed wine OK under my 32-bit chroot, but when I try and run an app (i.e. ie6setup.exe) I get: Invoking /usr/lib/wine/wine.bin ie6setup ... wine: Could not load graphics driver 'x11drv'. Make sure that your X server is running and that $DISPLAY is set correctly. Wine failed with return code 1 Any ideas? Thanks in advance. By the way, what should my $DISPLAY be? :0.0? How does it use the main display when in a dchroot? Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling module nvidia
Lennart Sorensen wrote: Mine is: http://www.tinyplanet.ca/~lsorense/debian/ Short and to the point and doens't involve recompiling a kernel. Mine's even shorter and to the point! ;-) Actually, I cheated. I stole bits of Len's howto (which is great - thanks), and put a few extras in. I found that most of my problems were a combination of not having the right apt-sources and having critical packages under /usr/src missing. This meant that some symbolic links were failing and causing the makefiles to fail. Note that this howto assumes that the kernel version is 2.6.8-11-amd64-generic, and that you haven't got a custom kernel. This is the current version AFAIK. Obviously, just swap all occurrences of this version string with whatever your uname -r gives you. Corrections/additions welcome. Simon == Debian amd64 nvidia howto === Make sure the following are in /etc/apt/sources.list: deb http://amd64.debian.net/debian-amd64 stable main non-free contrib deb http://amd64.debian.net/debian-amd64 unstable main non-free contrib Make sure you've got all the kernel sources - all these are needed as they have symbolic links in them. $ apt-get install kernel-kbuild-2.6-3 kernel-headers-2.6.8-11-amd64-generic kernel-headers-2.6.8-11 nvidia-kernel-source nvidia-kernel-common Get the module assistant: $ apt-get module-assistant Set up the appropriate kernel sources ready for the module assistant: $ m-a -i prepare Build the kernel module: $ m-a a-i -i -t -f nvidia-kernel Now get the other packages needed for getting the nvidia drivers working: $ apt-get install nvidia-glx nvidia-glx-dev If you haven't got xfree86 installed, install it: $ apt-get install xserver-xfree86 Otherwise, reconfigure it: $ dpkg-reconfigure xserver-xfree86 Select 'nvidia' for the driver when prompted. Enter whatever you want for the card name, and just press 'return' for the Bus Identifier and for amount of RAM. All other options depend on what you want. Best bet is to select 'simple' for the monitor configuration! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: FW: RE: x86_64 port
On 07 March 2005 18:01, Kurt Roeckx wrote:
> On Mon, Mar 07, 2005 at 11:47:31AM -0000, Simon Marlow wrote:
>>
>> $ cat bug.c
>> register void * R1 __asm__("%r13");
>>
>> extern void g(void);
>> static void f(void) {
>> R1 = g;
>> goto *R1;
>> }
>> $ gcc -S -O bug.c
>> $
>>
>> And take a look at the generated assembly for the function f:
>>
>> f:
>> .LFB2:
>> movl$g, %eax
>> jmp *%rax
>
> I get the same with both gcc-3.3 and gcc-3.4. They generate
> identical code.
>
>> Note that the assignment to the global variable R1 has been lost. It
>> works fine on x86 though: change the register variable to %esi and
>> try it.
>
> It looks to me like it's using eax/rax instead of r13 to me.
> It's probably doing some optimizing it shouldn't, but on the
> other hand isn't "wrong".
...
> Anyway, as summary:
> - It's using a movl where it should use a movq
> - It's probably doing some optimizations it shouldn't, but
> they're not "wrong" in this testcase and probably can't be
> avoided because of the way gcc works.
> Those happen on both i386 and amd64.
The question of whether this behaviour is wrong or not is interesting.
On the face of it, the generated code is incorrect because it doesn't
implement the semantics of the original program.
However, we have to be clear about what the semantics of the original
program *is*. The register annotation is just an annotation, and
therefore doesn't affect the semantics. But the gcc manual has this to
say about computed goto:
You may not use this mechanism to jump to code in a different
function.
So, perhaps the example program relies on undefined behaviour. But, you
can change the example program so that gcc has no idea where it's
jumping to, and gcc will still generate incorrect code. So in fact it
has nothing to do with the jump destination being outside the current
function.
It's a bug.
Cheers,
Simon
RE: FW: RE: x86_64 port
On 07 March 2005 16:40, Simon Marlow wrote:
> On 07 March 2005 16:18, David Brown wrote:
>
>> On Mon, Mar 07, 2005 at 11:47:31AM -, Simon Marlow wrote:
>>
>>> $ cat bug.c
>>> register void * R1 __asm__("%r13");
>>>
>>> extern void g(void);
>>> static void f(void) {
>>> R1 = g;
>>> goto *R1;
>>> }
>>> $ gcc -S -O bug.c
>>> $
>>>
>>> And take a look at the generated assembly for the function f:
>>>
>>> f:
>>> .LFB2:
>>> movl$g, %eax
>>> jmp *%rax
>>>
>>> Note that the assignment to the global variable R1 has been lost.
>>> It works fine on x86 though: change the register variable to %esi
>>> and try it.
>>
>> Hmm. On gcc 3.3.5 that I have, it discards the assignment on x86 as
>> well.
>
> Yes, looks like it fails with 3.4.1 and 3.4.3 I have here, but 3.2.2
> works.
>
> Now I'm quite surpised that this hasn't affected us on x86. Very
> strange.
The mystery as to why this doesn't affect us on x86 is solved: on x86 we
generate slightly different C code, including a dummy function call:
extern void g(void);
static void f(void) {
R1 = g;
dummy();
goto *R1;
}
the call to dummy() (which we filter out from the assembly later) is
enough to force gcc to emit the assignment to R1. That dummy function
call has been there for ever, and the original reason for it has been
lost in the mists of time... comments in the source code seemed to
indicate that it was probably not necessary any more, so for x86_64 I
removed it. It looks like I'll have to reinstate it to work around this
bug, though.
Cheers,
Simon
RE: FW: RE: x86_64 port
On 07 March 2005 16:18, David Brown wrote:
> On Mon, Mar 07, 2005 at 11:47:31AM -0000, Simon Marlow wrote:
>
>> $ cat bug.c
>> register void * R1 __asm__("%r13");
>>
>> extern void g(void);
>> static void f(void) {
>> R1 = g;
>> goto *R1;
>> }
>> $ gcc -S -O bug.c
>> $
>>
>> And take a look at the generated assembly for the function f:
>>
>> f:
>> .LFB2:
>> movl$g, %eax
>> jmp *%rax
>>
>> Note that the assignment to the global variable R1 has been lost. It
>> works fine on x86 though: change the register variable to %esi and
>> try it.
>
> Hmm. On gcc 3.3.5 that I have, it discards the assignment on x86 as
> well.
Yes, looks like it fails with 3.4.1 and 3.4.3 I have here, but 3.2.2
works.
Now I'm quite surpised that this hasn't affected us on x86. Very
strange.
Cheers,
Simon
RE: FW: RE: x86_64 port
On 04 March 2005 17:32, Kurt Roeckx wrote:
> I have no idea what ghc has too do with gcc,
A bit of background: GHC uses gcc as a backend compiler. GHC generates
C code that is compiled using gcc (we also have a native code generator
for some platforms; but not for x86_64 yet).
> or what the problem exactly is.
The problem is that gcc generates incorrect code for C code that uses
global register variables. You won't have noticed this, because most
programs don't use global register variables. GHC uses global register
variables to speed up the generated code.
> We have very little problems with gcc for the debian
> amd64 port. Our default compiler is still 3.3. This builds
> almost everything without problems, however we build a few
> mozilla packages with gcc-3.4.
>
> All I can tell is that ghc6 seems to be working on debian amd64.
> It can build itself and things like that.
That build of ghc6 is what we call "unregisterised": it doesn't make use
of register variables to speed up the generated code. IOW, it generates
plain ANSI C code, which gcc compiles fine.
> Can someone please give a test case (and show what to do) to see
> what is wrong?
Ok, here's a really simple example:
$ cat bug.c
register void * R1 __asm__("%r13");
extern void g(void);
static void f(void) {
R1 = g;
goto *R1;
}
$ gcc -S -O bug.c
$
And take a look at the generated assembly for the function f:
f:
.LFB2:
movl$g, %eax
jmp *%rax
Note that the assignment to the global variable R1 has been lost. It
works fine on x86 though: change the register variable to %esi and try
it.
> Out current default compiler in debian is:
> gcc version 3.3.5 (Debian 1:3.3.5-8)
>
> The gcc 3.4 version is:
> gcc version 3.4.4 20050203 (prerelease) (Debian 3.4.3-9)
>
> And ghc6 is at version 6.2.2-3.
I'm going to try with different versions of gcc. I've just submitted
this bug report to the gcc guys.
Cheers,
Simon
Error apt-getting new EM64T kernel (anyone?)
Is anybody out there.. Original Message Subject: Error apt-getting new EM64T kernel Resent-Date: Thu, 9 Dec 2004 14:44:49 -0600 (CST) Resent-From: debian-amd64@lists.debian.org Date: Fri, 10 Dec 2004 09:44:45 +1300 From: Simon Buchanan <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Hi There, I have just completed install of debian testing on my new SMP server (xeon nocona processors) and went to install a new SMP-aware kernel and got this message: dpkg: error processing /var/cache/apt/archives/kernel-image-2.6.8-9-em64t-p4-smp_2.6.8-5_i386.deb (--unpack): subprocess pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/kernel-image-2.6.8-9-em64t-p4-smp_2.6.8-5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Any thoughts here? Is this a bug? I tryed the standard "kernel-image-2.6.8-1-686-smp" version and it installed correctly... Thanks and Regards, Simon -- This message was scanned for spam and viruses by BitDefender For more information please visit http://linux.bitdefender.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- This message was scanned for spam and viruses by BitDefender For more information please visit http://linux.bitdefender.com/
Error apt-getting new EM64T kernel
Hi There, I have just completed install of debian testing on my new SMP server (xeon nocona processors) and went to install a new SMP-aware kernel and got this message: dpkg: error processing /var/cache/apt/archives/kernel-image-2.6.8-9-em64t-p4-smp_2.6.8-5_i386.deb (--unpack): subprocess pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/kernel-image-2.6.8-9-em64t-p4-smp_2.6.8-5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Any thoughts here? Is this a bug? I tryed the standard "kernel-image-2.6.8-1-686-smp" version and it installed correctly... Thanks and Regards, Simon -- This message was scanned for spam and viruses by BitDefender For more information please visit http://linux.bitdefender.com/
AMD64 Question
Hi There, Can someone please answer a hardware/usage question for me? We have used woody on 386/686 servers for ages, normally on pentium 3 and AMD athlons. We are currently susing a new production mail server... which will have the following installed: - Postfix, DBMail, Apache, PHP, MySQL and a virus product called BitDefender The servers spec is currently: - Tyan Tiger 7320 motherboard, 2xXeon (800Mhz), 2GB RAM, 3Ware 9000 SATA hardware Raid (PCI-X), Intel nics. My question is: Above sinatlling sarge and running this kernel "kernel-image-2.6.8-9-em64t-p4-smp", is it worth looking at the AMD64 debian port for this server? bearing in mind that it is a production system and needs to be a high-availability one at that. Thanks (sorry for the green question) Simon -- This message was scanned for spam and viruses by BitDefender For more information please visit http://linux.bitdefender.com/
Re: External hard drive problem
On Thursday 16 Sep 2004 10:45, Karl Hegbloom wrote: > On Thu, 2004-09-16 at 09:52 +0200, Massimo Perga wrote: > > Please, could you help me ? > > I don't think that the installer will support installing to a firewire > drive right now. (unless they fixed that) You may be able to get it to > work installing by hand with 'Debian from scratch'. > > -- > Karl Hegbloom > (o_ mailto:[EMAIL PROTECTED] > //\ jabber:[EMAIL PROTECTED] > V_/_ yahoo:karlheg Another method maybe to boot from a Knoppix CD where you should be able to access the disk, partition it, format it and install debian from Knoppix. The problem will come when trying to boot Linux from the firewire disk. Perhaps you create a Linux boot CD that can find the firewire disk and then start the boot process on it. This all sounds like advanced stuff so I wouldn't recommend it if you're just starting out with Linux. The easiest way for you to use Linux without touching the HD in your laptop would be to simply use and run a Knoppix CD. You could use your firewire HD to store all your linux related data. http://knoppix.org/ Simon
