Re: beta status
On Sun, Nov 06, 2005 at 06:27:52PM -0500, Joey Hess wrote: > Kurt Roeckx wrote: > > I would be suprised if it generated broken .changes files. I've > > attached it. > > It's broken, what's the listed debian-installer_20051026_amd64.deb? dpkg -I debian-installer_20051026_amd64.deb new debian package, version 2.0. size 574138 bytes: control archive= 370 bytes. 356 bytes,10 lines control Package: debian-installer Version: 20051026 Section: devel Priority: optional Architecture: amd64 Installed-Size: 1316 Maintainer: Debian Install System Team Description: Debian installer This package currently only contains some documentation for the Debian installer. We welcome suggestions about what else to put in it. And it contains things in /usr/share/doc. It's also the only thing that is actually in debian/control. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nvidia 7174 + 2.6.12 kernel problem (sid)
Hey, nice work with that! 1 warning about it being unable to delete the directory created in /var, but other than that, it was totally clean.On 11/5/05, v0n0 < [EMAIL PROTECTED]> wrote:Grahame White ha scritto:>Looking back a bit I see you were asking about a clean way to install the >newer drivers. I couldn't, however, find any reply. How did you install>them in the end?>>If you want you can try my nvidia-update:http://v0n0.altervista.org/ --Alessandro Dal GrandeStudent In The University Of Padua - Computer ScienceLinux Registered User #359258System: GNU/Linux Debian Sid Pure64 on [EMAIL PROTECTED]Chat: Psi ICQ) 150487234 Jabber) [EMAIL PROTECTED]Home: http://v0n0.altervista.org
Re: problems with installation
Hi Jean. Try manually selecting the forcedeth (nVidia) network card from the list on the sarge CD. I had a similar problem with my Gigabyte motherbard, which has an nForce4 chipset. I used the AMD64 Sarge netboot CD, and it wouldn't automagically detect my network card, I manually selected the forcedeth card and the module loaded, no complaints. As for sound, I believe after I had everything up and running I had to apt-get all the alsa stuff and then used module-assistant to get my sound up and running. Todd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems to link /usr/lib32/libpng.so.2 for Panotools 32bit
Gerhard Gaußling wrote: > Now I tried to use a script in hugin to use the 32bit chroot for > PTStitcher, but it doesn't works. > > ~/bin/PTStitcher > #!/bin/bash > dchroot -c i386_chroot -d PTStitcher $1 $2 $3 $4 > exit > > So, I'm not a good scripter and there might be a problem with $1 $2 $3 > $4 ;-). Yes, that was the problem. Here is the right line: dchroot -c i386_chroot -d PTStitcher "$@" > But anyway: I want to know how to link the 32bit png lib the right way, to > use PTStitcher and the other 32bit panotools from > http://www.path.unimelb.edu.au/~dersch/ > http://www.path.unimelb.edu.au/~dersch/PanoTools.tar.gz > on my amd64 x86_64 breezy box. Yes, I'm still curious about this mysterious linker story. Any insights? Any hints are grately appreciate! Kind regards Gerhard Gaußling -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: beta status
Kurt Roeckx wrote: > I would be suprised if it generated broken .changes files. I've > attached it. It's broken, what's the listed debian-installer_20051026_amd64.deb? > Files: > cf4dca5ef36c3ab9e8794be42533fd5e 574138 devel optional > debian-installer_20051026_amd64.deb > 35a90f59e9d7ee2694ad2e94e1b30746 49826709 raw-installer - > debian-installer-images_20051026_amd64.tar.gz Should list only the second of these. -- see shy jo signature.asc Description: Digital signature
Re: beta status
On Sun, Nov 06, 2005 at 02:39:38PM -0500, Joey Hess wrote: > Kurt Roeckx wrote: > > 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. > > > > It also did that with the previous version that build > > (20051009), and I have no idea why. > > > > It seems to think that > > debian-installer-images_20051026_amd64.tar.gz is the > > source while it's actually a (special) binary package. > > Sounds to me like a broken .changes file.. I would be suprised if it generated broken .changes files. I've attached it. Kurt -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Oct 2005 18:55:45 -0400 Source: debian-installer Binary: debian-installer Architecture: amd64 Version: 20051026 Distribution: unstable Urgency: low Maintainer: Kurt Roeckx <[EMAIL PROTECTED]> Changed-By: Joey Hess <[EMAIL PROTECTED]> Description: debian-installer - Debian installer Closes: 334780 Changes: debian-installer (20051026) unstable; urgency=low . [ Joey Hess ] * Add cramfsprogs dependency for mipsel. Closes: #334780 * Syslinux ignores failures due to being out of disk space (#335152). Avoid this bug by running syslinux on the original, empty disk image. * If the boot logo can't be copied onto a floppy, don't fail, just proceed on without a boot logo. Yes, we're that short on space on the i386 boot floppies, no more logos for them until space is freed up. * Deal with changed case of Kernel-Version fields in stat generation code. . [ Colin Watson ] * Improve wording of debian-installer binary package description. Files: cf4dca5ef36c3ab9e8794be42533fd5e 574138 devel optional debian-installer_20051026_amd64.deb 35a90f59e9d7ee2694ad2e94e1b30746 49826709 raw-installer - debian-installer-images_20051026_amd64.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDbKoLQdwckHJElwsRAhl2AJsE8s2MViJ71sEhAB/KG52X/Z7vAACg5uN5 458rVpt0tO9fnElMPON6Uao= =EAQJ -END PGP SIGNATURE-
Re: beta status
Kurt Roeckx wrote: > 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. > > It also did that with the previous version that build > (20051009), and I have no idea why. > > It seems to think that > debian-installer-images_20051026_amd64.tar.gz is the > source while it's actually a (special) binary package. Sounds to me like a broken .changes file.. -- see shy jo signature.asc Description: Digital signature
On laptop: "Display changed: LCD off/on" problem
Hello, A few days ago, using KPackage, I upgraded Quanta on my laptop and this lead to a more general upgrade from KDE 3.3 to KDE 3.4. There was globally no trouble except that now, from time to time (i.e. once every few minutes) I have a message on the midlle of my screen saying "Display changed: LCD on". I don't really have time to see anything else, but I suspect there is a previous message, which disappears immediately, that says "Display changed: LCD off". Of course, I'm never changing the display. I looked in the syslog but I didn't find any useful information. Has anyone already seen that? - Emmanuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Install on Sager np4750, Problems with Realtek r8169 ethernet driver
Hi everybody, I have a new Sager np4750 laptop that has a Realtek gigabit ethernet card that uses the r8169 driver in the kernel. On doing the amd64 install, Debian identified the card without problem. I can load the module and bring up the eth0 network interface. However, I can't pass any traffic, either by DNS or by IP address (I can't even ping my gateway). I get an error message "Netdev Watchdog: eth0: transmit timed out". I have tried building a new stock kernel (2.6.14) but the result wasn't any different. I then tried building the driver as downloaded from Realtek's website, but it failed to build. I don't know if that problem pertains to the driver's code, or simply with trying to build it for amd64 (sorry, this is my first amd64 CPU -- so I'm new to 64 bit computing). Has anybody else had a similar problem with the r8169? Should I first try to install the 32 bit version of Debian to verify that it will work in that version? I guess I just don't know if this is just an r8169 driver problem, or a problem with it in the Debian amd64 port, or something else. I have found some other linux users (Mandrake and Gentoo users) on the web using this driver in the 64bit versions of their distro, without problem. Can anybody help? Thanks! Bryan Walton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: #298152: checkinstall: incorrectly sets Arch:x86_64 for .deb under amd64
Kurt Roeckx @ 2005-06-12 (Sunday), 23:05 (+0200) > You should be using something like dpkg --print-architecture or > dpkg-architecture instead. Would this patch do the trick? -- /Martin diff -ur checkinstall-1.5.3/checkinstall checkinstall-patched-1.5.3/checkinstall --- checkinstall-1.5.3/checkinstall 2005-11-06 14:03:59.302390154 +0100 +++ checkinstall-patched-1.5.3/checkinstall 2005-11-06 14:10:20.886160966 +0100 @@ -1146,8 +1146,8 @@ # Fix the PowerPC architecture description if we're on Debian - if [ "$CK_DEBIAN" = "1" ] && [ "$ARCHITECTURE" = "ppc" ]; then - ARCHITECTURE="powerpc" + if [ "$CK_DEBIAN" = "1" ] then + ARCHITECTURE=`dpkg-architecture -qDEB_HOST_ARCH` fi
Re: newbie question
On November 6, 2005 02:00 am, Danny tiberman wrote: > hello, > > I am trying to compile kernel 2.6.12 but I am getting kernel panic > apparently it does not recognize my sata disk > > does anyone got suggestions ? Make sure you have support for promise sata support in "block devices" for a start. (assuming you have a promise sata controller) why aren't you compiling the latest kernel? Chris W. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
newbie question
hello, I am trying to compile kernel 2.6.12 but I am getting kernel panic apparently it does not recognize my sata disk does anyone got suggestions ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
In comparing the unofficial sarge to the sid_d-i CD, I find that I'm able to partition as I hope/expect with sid: disk1 1 small physical volume for RAID for /boot 1 large physical volume for RAID for rest of system disk2 1 small physical volume for RAID for /boot 1 large physical volume for RAID for rest of system RAID1 Use as ext3 for /boot RAID1 physical volume for LVM LVM vg0 root var swap home After doing so, LILO installs just fine (whereas it punks out in the sarge installer). This suggests a limitation at some level in sarge (whether kernel, installer, or LILO I don't know). Is this the sort of thing that's likely to get fixed in sarge, or should I just stick with sid? If any of this is not a known bug, I'd be happy to file one. -- 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]
