Idea for structure of Apt-Get
Hello. I'm not sure if anyone has suggested something like this or not but I was thinking about the apt-get system and bittorrent today. What if the apt-get system was redesigned so that users could download updates and upgrades from other users? This way they would trickle out to people, slowly at first, but then more and more people would have the update and thus more people could get it faster. I know there would probably be a lot of security issues involved but then maybe people wouldn't have to worry about setting up .deb mirrors and trying to get the latest upgrades. Just a thought. If it's a bad one, let me know. :) -Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248043: ftp.debian.org: Request for new architecture: amd64
On Sat, May 08, 2004 at 10:03:13PM +0200, Goswin Brederlow wrote: > the debian amd64 port is rapidly maturing and apart from beeing so new > its reaching a point where the goals needed for it to be released > would be met (i.e. D-I support, most packages compiled, ...). > > Amd64 was recently discussed on debian-devel > > http://lists.debian.org/debian-devel/2004/05/msg00412.html > > and this is a formalization of that discussion asking for amd64 to be > added to _sid_. If there are any reasons for not adding amd64 please > do tell so we can eliminate them. This will happen post-sarge, amd64 will not get released with sarge, and adding it to sid now would only cause more work that can better be spent elsewhere (read: releasing sarge). --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] http://jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: un-ported list
On Fri, Mar 18, 2005 at 06:43:38PM -0500, Javier Kohen wrote: > > What packages in main provide java2-compiler? Practically every package > that's waiting for a dependency blames that one. None provide it. Those packages are also all in contrib for that reason. They are provided by packages as sun's or blackdown's java compilers. Note that most of those packages actually have been tried with one of those but failed for one reason or an other. They probably don't have bugs filed. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: un-ported list
El sÃb, 19-03-2005 a las 00:30 +0100, Kurt Roeckx escribiÃ: > On Fri, Mar 18, 2005 at 05:57:42PM -0500, Tong wrote: > > Hi, > > > > Since about 99% of packages have been ported to AMD64, I'm wondering where > > I can obtain a list of packages that are not available in AMD64 yet. > > > > PS. I found 2 files on alioth, but I didn't find the ooffice there: > > > > http://debian-amd64.alioth.debian.org/pure64/needs-porting.txt > > http://debian-amd64.alioth.debian.org/pure64/failed.txt > > Also see not-for-us.txt and dep-wait.txt (I just created those.) What packages in main provide java2-compiler? Practically every package that's waiting for a dependency blames that one. Thanks, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] signature.asc Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente
Re: harddisk DMA
On Friday 18 March 2005 14:54, Lennart Sorensen wrote: > > Could you include the section of dmesg where ide is detected and setup? > Gotta make sure it didn't load ide-generic before the sis driver in > which case the generic driver (which is not dma capable obviously) is > running the drives instead of the native sis driver (which likely does > support dma). > > Also which model HD is it? Some are blicklisted in the kernel for > having some firmware bug that makes the drive unreliable with dma > enabled on certain controllers. > > Len Sorensen Hi Len, here is the corresponding snippet of dmesg. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx SIS5513: IDE controller at PCI slot :00:02.5 SIS5513: chipset revision 1 SIS5513: not 100% native mode: will probe irqs later Probing IDE interface ide0... hda: IC35L080AVVA07-0, ATA DISK drive hdb: HL-DT-ST DVDRAM GSA-4163B, ATAPI CD/DVD-ROM drive Probing IDE interface ide1... hdc: HDS722525VLAT80, ATA DISK drive Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... elevator: using anticipatory as default io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 160836480 sectors (82348 MB) w/1863KiB Cache, CHS=65535/16/63 hda: cache flushes supported /dev/ide/host0/bus0/target0/lun0: p1 p2 hdc: max request size: 1024KiB hdc: 488397168 sectors (250059 MB) w/7938KiB Cache, CHS=30401/255/63 hdc: cache flushes supported /dev/ide/host1/bus0/target0/lun0: p1 my harddrives are both newer hitachi 80/250GB. I commented out the generic part in /etc/modules and added sis5513 at the first line. but lsmod still mentions this: ide_core 146948 28 ide_cd,ide_generic,via82cxxx,trm290,triflex,slc90e66,sis5513,siimage,serverworks,sc1200,rz1000,piix,pdc202xx_old,opti621,ns87415,hpt366,ide_disk,hpt34x,generic,cy82c693,cs5530,cs5520,cmd64x,atiixp,amd74xx,alim15x3,aec62xx,pdc202xx_new this looks horrible to me. i don't know, how that hotplug-thing is working maybe it is due some action it does... greetings Uwe -- --- ASUS K8S-MX, 2800+ (754), 512MB, gnuLinux v2.6.x -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: un-ported list
On Fri, Mar 18, 2005 at 05:57:42PM -0500, Tong wrote: > Hi, > > Since about 99% of packages have been ported to AMD64, I'm wondering where > I can obtain a list of packages that are not available in AMD64 yet. > > PS. I found 2 files on alioth, but I didn't find the ooffice there: > > http://debian-amd64.alioth.debian.org/pure64/needs-porting.txt > http://debian-amd64.alioth.debian.org/pure64/failed.txt Also see not-for-us.txt and dep-wait.txt (I just created those.) Note that this information is also available from www.buildd.net Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
On Fri, 11 Mar 2005 11:26:02 -0700, Bob Proulx wrote: >> /emul/ia32-linux/usr/lib in my ldconfig, and running openoffice works >> fine without having to chroot or anything. > > Running it outside the chroot needs a symlink. See this thread. > > http://lists.debian.org/debian-ia64/2003/03/msg00012.html > > But it works fine with the symlink in place. Thanks a lot, Bob! That's a very insightful post -- just what I was hoping to achieve... save me tons of trials and errors. How about david's tip on 'no-need-symlinks'? ,- | If you use /emul/ia32-linux/ instead of /woody-ia32, you don't need | any of this symlink magic. For x86 apps, the kernel will | automatically check for a file in /emul/ia32-linux before trying to | open it starting from root. (Details are in my book on page 464.) | `- Do you have new updates on that? Have you run a strace to verify? thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
un-ported list
Hi, Since about 99% of packages have been ported to AMD64, I'm wondering where I can obtain a list of packages that are not available in AMD64 yet. PS. I found 2 files on alioth, but I didn't find the ooffice there: http://debian-amd64.alioth.debian.org/pure64/needs-porting.txt http://debian-amd64.alioth.debian.org/pure64/failed.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Fri, 18 Mar 2005 21:43:06 +0100, Ernest jw ter Kuile wrote: > On Friday 18 March 2005 21:15, Hannes Mayer wrote: > > It should probably say "is a static executable". That would be more clear. > > > > Not necesserally, it could be anything else too. it could be a script, a > picture, a device, etc ..., or a static excecutable. > > ldd had only one error for all files it does not understand, which is this > one. > it is not ldd's role to figure out _what_ the file is. you could have used > 'file' for that. > > see here the difference : > > $> ldd /bin/mbchk > not a dynamic executable > > $> file /bin/mbchk > /bin/mbchk: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for > GNU/Linux 2.2.0, statically linked, stripped > > and for a picture (which happen to have the x bit set): > > $> ldd pictures/dsc00045.jpg > not a dynamic executable > > $> file pictures/dsc00045.jpg > pictures/dsc00045.jpg: JPEG image data, EXIF standard Thanks a lot for the explanation Ernest! # file pptp pppd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, statically linked, stripped :-) Best regards, Hannes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Fri, 2005-03-18 at 21:07 +0100, Hannes Mayer wrote: > First I tried to use pptp from alioth, but that did not work, so as a > last resort I tried to run the 32bit versions and voila! They worked! Definitely check your PPTP settings. If you want the best encryption and compression, you'll have to recompile your kernel with a couple patches. If poorly configured (server and client sides), you could be sending clear text packets! -s signature.asc Description: This is a digitally signed message part
Re: 32bit binaries run on pure64!?
On Friday 18 March 2005 21:15, Hannes Mayer wrote: > It should probably say "is a static executable". That would be more clear. > Not necesserally, it could be anything else too. it could be a script, a picture, a device, etc ..., or a static excecutable. ldd had only one error for all files it does not understand, which is this one. it is not ldd's role to figure out _what_ the file is. you could have used 'file' for that. see here the difference : $> ldd /bin/mbchk not a dynamic executable $> file /bin/mbchk /bin/mbchk: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, statically linked, stripped and for a picture (which happen to have the x bit set): $> ldd pictures/dsc00045.jpg not a dynamic executable $> file pictures/dsc00045.jpg pictures/dsc00045.jpg: JPEG image data, EXIF standard Cheers, Ernest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Fri, 18 Mar 2005 21:06:53 +0100, Ernest jw ter Kuile <[EMAIL PROTECTED]> wrote: > > not a dynamic executable > > Indeed: Static > > ;o) Thanks Ernest! The message is a bit confusing. At least I was confused, since it said it is "not a ... executable". It should probably say "is a static executable". That would be more clear. Thanks again & best regards, Hannes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Fri, 18 Mar 2005 14:51:57 -0500, Lennart Sorensen wrote: > On Fri, Mar 18, 2005 at 08:36:26PM +0100, Hannes Mayer wrote: [...] > > # ldd pppd > > /usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such file or directory > > ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) > > That means it is a dynamicly built binary and your system doesn't have > 32bit runtime libraries installed. ld-linux.so.2 is provided by the > 32bit version of libc6. Ahh! Thanks! > If they are staticly built they should just run if you try to run them I > believe. > > Either install the 32bit libs package or find the equivalant debian > programs in 64bit packages and use those instead (highly recomended). > You can still use the scripts provided. First I tried to use pptp from alioth, but that did not work, so as a last resort I tried to run the 32bit versions and voila! They worked! :-) I just installed ia32-libs: ld-linux.so.2 -> /emul/ia32-linux/lib/ld-linux.so.2 is there # ldd pptp not a dynamic executable Well, those binaries are possibly linked statically, but it works :-) Thanks & best regards, Hannes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
> not a dynamic executable Indeed: Static ;o) Ernest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Fri, Mar 18, 2005 at 08:36:26PM +0100, Hannes Mayer wrote: > On Fri, 18 Mar 2005 13:20:08 -0600, Stephen Waters wrote: > > On Fri, 2005-03-18 at 20:15 +0100, Hannes Mayer wrote: > [...] > > > How come that 32bit binaries run on pure64 without any chroot or the > > > ia32 libs installed ? > > > > They're probably statically compiled so they'll work on any system. Run > > ldd on one of the binaries and it'll tell ya what it links to (very > > likely, nothing). > Ahh! Didn't consider that they are compiled statically. > But ldd seems to be broken: > # ldd pppd > /usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such file or directory > ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) That means it is a dynamicly built binary and your system doesn't have 32bit runtime libraries installed. ld-linux.so.2 is provided by the 32bit version of libc6. > # ldd pptp > /usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such file or directory > ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) > # ldd dhcpcd > /usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such file or directory > ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) Same as above. > So I tried to make a symlink: > debian:/lib# ln -s ld-2.3.2.so ld-linux.so.2 > But: > # ldd pptp > not a dynamic executable It doesn't work that way. If it is a dynamic library it needs the 32bit libs to even look at it. The 64bit libs won't work with it so ldd won't work with it. If they are staticly built they should just run if you try to run them I believe. Either install the 32bit libs package or find the equivalant debian programs in 64bit packages and use those instead (highly recomended). You can still use the scripts provided. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Fri, 18 Mar 2005 13:20:08 -0600, Stephen Waters wrote: > On Fri, 2005-03-18 at 20:15 +0100, Hannes Mayer wrote: [...] > > How come that 32bit binaries run on pure64 without any chroot or the > > ia32 libs installed ? > > They're probably statically compiled so they'll work on any system. Run > ldd on one of the binaries and it'll tell ya what it links to (very > likely, nothing). Hi Stephen! Ahh! Didn't consider that they are compiled statically. But ldd seems to be broken: # ldd pppd /usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such file or directory ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) # ldd pptp /usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such file or directory ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) # ldd dhcpcd /usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such file or directory ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) So I tried to make a symlink: debian:/lib# ln -s ld-2.3.2.so ld-linux.so.2 But: # ldd pptp not a dynamic executable Thanks & best regards, Hannes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Friday 18 March 2005 20:15, Hannes Mayer wrote: > How come that 32bit binaries run on pure64 without any chroot or the > ia32 libs installed ? They are probably statically linked. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit binaries run on pure64!?
On Fri, Mar 18, 2005 at 08:15:49PM +0100, Hannes Mayer wrote: > I just installed pure64 on a spare disk for testing. > In order to connect to the net, I got a tar.gz from my provider with > precompiled binaries of dhcpcd, pptp, and pppd and some scripts. It > works very well on sarge (32bit) but surprisingly enough those > binaries also work on pure64! > > How come that 32bit binaries run on pure64 without any chroot or the > ia32 libs installed ? > > Note: No ia32 libs installed: > # dpkg -l ia32\* Well dhcpcd and pppd certainly exist in debian packages (which would hence be far preferable to use). As for pptp, it probably exists too, but I am not sure how good the support in linux is for that since it is not widely used nor considered a very good protocol to use. You would certainly need some 32bit libs installed if the binaries aren't compiled staticly. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
32bit binaries run on pure64!?
Hi all! I just installed pure64 on a spare disk for testing. In order to connect to the net, I got a tar.gz from my provider with precompiled binaries of dhcpcd, pptp, and pppd and some scripts. It works very well on sarge (32bit) but surprisingly enough those binaries also work on pure64! How come that 32bit binaries run on pure64 without any chroot or the ia32 libs installed ? Note: No ia32 libs installed: # dpkg -l ia32\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== pn ia32-libs (no description available) pn ia32-libs-dev (no description available) pn ia32-libs-openoffice.org (no description available) Thanks & best regards, Hannes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
OpenOffice for AMD64
Hi folks I searched on the oficele OpenOffice Homepage for a port on the amd64. In the mailing-list I found something about a cvs-version. do anyone of you have installed it on his system and made experiences with it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SATA/IDE strangeness (ATI chip)
Hi, On Thu, 17 Mar 2005 18:55:22 +0100, Oliver Korpilla <[EMAIL PROTECTED]> wrote: > Hello! > > On my MSI motherboard there are the following devices: > > :00:11.0 IDE interface: ATI Technologies Inc: Unknown device 437a > :00:12.0 IDE interface: ATI Technologies Inc: Unknown device 4379 > :00:14.1 IDE interface: ATI Technologies Inc: Unknown device 4376 > > These are listed in the PCI ID database (not committed yet): > > 4376Standard Dual Channel PCI IDE Controller ATI > 4379ATI 4379 Serial ATA Controller > 437aATI 437A Serial ATA Controller > > The 1st SATA controller seems to work with the SATA_SIL driver from > vanilla 2.6.11 (and none sooner, I tried), and I'm using it that way > now. Since the Debian Pure64 CD doesn't come with that, it doesn't find > a HD when trying to install with the CD. > > I have the following problems: > -- > * Though the SATA is configured in IDE mode in BIOS it does not show up > as IDE within Linux and this does not change when the ATIIXP driver is > loaded - ide2 is not recognized as a bus with connected devices. My SATA > HD is listed by the BIOS to be channel 2 master, while CD-ROM on the > Dual ATA is listed on channel 0, channel 1 is unused, so shouldn't the > SATA drive show up as /dev/hde or something??? Linux no longer use legacy/obsolete BIOS ordering/naming. You can name /dev nodes however you want using udev. > * How can I tune the ATIIXP driver via parameters or source modification > so it recognizes the SATA controllers as devices to configure??? What for? > * How can I force ANY IDE driver to recognize these SATA drives in IDE > mode? > > This is a mail regarding this topic I'm confused about. The author seems > to think, ATIIXP can do the 4379 as well: It can't (reliably). > http://www.ussg.iu.edu/hypermail/linux/kernel/0412.1/1460.html > > Please let me know if I can provide you with any additional data. > > Thanks and with kind regards, > Oliver Korpilla -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Zero latency kernel 2.6.10 (64 bit)
On Fri, Mar 18, 2005 at 09:45:18AM +, Daniel James wrote: > DeMuDi still uses XFree86 rather than X.org for the time being, the > monitor autodetection doesn't work properly, and dpkg-reconfigure > xserver-xfree86 doesn't overwrite /etc/X11/XF86Config-4 like it > should, for some reason. Perhaps you're running into this (from /etc/X11/XF86Config-4): # If you have edited this file but would like it to be automatically # updated again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 >/var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 dpkg-reconfigure isn't willing to overwrite an XF86Config-4 that it doesn't think it previously wrote. The above tricks it into thinking it wrote it, even if you have hand-edited it in the past. HTH, --Pete -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: harddisk DMA
*** Regarding harddisk DMA; Uwe <[EMAIL PROTECTED]> adds: Uwe> i have 2.6.10-9 installed on SIS chipset hardware. the Uwe> SIS5513 module is loaded, but doesn't work with DMA support for Uwe> my harddisks. hdparm -d1 /dev/hda tells me that this operation Uwe> is not supported: I had a similar problem with my nForce 3 250G based board. It turned out to be due to the ide-generic kernel module being loaded before the chipset specific driver. Check your /etc/modules file and see if ide-generic is being loaded, and if it is, remove it and replace the line with your SIS5513 module. I found I had to load my module before ide-cd. Per -- Per Bojsen <[EMAIL PROTECTED]> 7 Francis Road Billerica, MA 01821-3618 USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: harddisk DMA
On Sat, Mar 19, 2005 at 09:04:07AM +0100, Uwe wrote: > hi there, > > i have 2.6.10-9 installed on SIS chipset hardware. the SIS5513 module is > loaded, but doesn't work with DMA support for my harddisks. > hdparm -d1 /dev/hda tells me that this operation is not supported: > > filou:~# cat /proc/ide/hda/settings > namevalue min max mode > - --- --- > acoustic0 0 254 rw > address 0 0 2 rw > bios_cyl65535 0 65535 rw > bios_head 16 0 255 rw > bios_sect 63 0 63 rw > bswap 0 0 1 r > current_speed 0 0 70 rw > failures0 0 65535 rw > init_speed 0 0 70 rw > io_32bit0 0 3 rw > keepsettings0 0 1 rw > lun 0 0 7 rw > max_failures1 0 65535 rw > multcount 0 0 16 rw > nice1 1 0 1 rw > nowerr 0 0 1 rw > number 0 0 3 rw > pio_modewrite-only 0 255 w > unmaskirq 0 0 1 rw > using_dma 0 0 1 rw > wcache 1 0 1 rw > filou:~# > filou:~# hdparm -d1 /dev/hda > > /dev/hda: > setting using_dma to 1 (on) > HDIO_SET_DMA failed: Operation not permitted > using_dma= 0 (off) > filou:~# > > > i have no idea, weher to start searching. there is also some misterious dmesg > message: > > PCI: Using ACPI for IRQ routing > ** Routing PCI interrupts for all devices because "pci=routeirq" > ** was specified. If this was required to make a driver work, > ** please email the output of "lspci" to [EMAIL PROTECTED] > ** so I can fix the driver. > ACPI: PCI interrupt :00:02.7[C] -> GSI 18 (level, low) -> IRQ 18 > ACPI: PCI interrupt :00:03.0[A] -> GSI 20 (level, low) -> IRQ 20 > ACPI: PCI interrupt :00:03.1[B] -> GSI 21 (level, low) -> IRQ 21 > ACPI: PCI interrupt :00:03.2[C] -> GSI 22 (level, low) -> IRQ 22 > ACPI: PCI interrupt :00:03.3[D] -> GSI 23 (level, low) -> IRQ 23 > ACPI: PCI interrupt :00:04.0[A] -> GSI 19 (level, low) -> IRQ 19 > ACPI: PCI interrupt :00:05.0[A] -> GSI 17 (level, low) -> IRQ 17 > ACPI: PCI interrupt :00:06.0[A] -> GSI 16 (level, low) -> IRQ 16 > ACPI: PCI interrupt :00:07.0[A] -> GSI 16 (level, low) -> IRQ 16 > ACPI: PCI interrupt :00:09.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI-DMA: Disabling IOMMU. > > but i don't know if this corresponds to a non working ide-dma... Could you include the section of dmesg where ide is detected and setup? Gotta make sure it didn't load ide-generic before the sis driver in which case the generic driver (which is not dma capable obviously) is running the drives instead of the native sis driver (which likely does support dma). Also which model HD is it? Some are blicklisted in the kernel for having some firmware bug that makes the drive unreliable with dma enabled on certain controllers. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with htDig
Le vendredi 18 mars 2005 à 08:23 +0100, Egon Willighagen a écrit : HtDig 3.2 compiles out of the box, and works well (a bit slow...) but i think there's no debian package yet (has been announced ?.?.)... I've not tried yet to recompile 3.1.6. > And I was thinking that I did something wrong ! :( [EMAIL PROTECTED]@@[EMAIL > PROTECTED]@ The same for me... a linux reflex : human error, and then software error (that's a bit different for other $OSes)... in fact, you can event have human error / hardware error / software error (on a good old woody server, for example) :-) JMB > Egon > > signature.asc Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Re: Zero latency kernel 2.6.10 (64 bit)
Oh ok! I'll give that a go when I get home from work :) Daniel James <[EMAIL PROTECTED]> wrote : > Hi James, > > > I've installed DeMuDi on the other 6gb hard drive here. Install > > went fine, but X wont be starting. > > DeMuDi still uses XFree86 rather than X.org for the time being, the > monitor autodetection doesn't work properly, and dpkg-reconfigure > xserver-xfree86 doesn't overwrite /etc/X11/XF86Config-4 like it > should, for some reason. > > I suggest hand-editing that file in the console (ctrl-alt-F1) - take a > look at the entry under Section "Monitor". Overwrite the vertical > and > > horizontal refresh ranges using the numbers from your monitor > documentation. Then do a ctrl-alt-backspace and X should come up with > a gdm login screen. > > Cheers > > Daniel ___ Sent Using: Total Carnage WebMail, with NOCC, http://nocc.sourceforge.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Zero latency kernel 2.6.10 (64 bit)
Hi James, > I've installed DeMuDi on the other 6gb hard drive here. Install > went fine, but X wont be starting. DeMuDi still uses XFree86 rather than X.org for the time being, the monitor autodetection doesn't work properly, and dpkg-reconfigure xserver-xfree86 doesn't overwrite /etc/X11/XF86Config-4 like it should, for some reason. I suggest hand-editing that file in the console (ctrl-alt-F1) - take a look at the entry under Section "Monitor". Overwrite the vertical and horizontal refresh ranges using the numbers from your monitor documentation. Then do a ctrl-alt-backspace and X should come up with a gdm login screen. Cheers Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Zero latency kernel 2.6.10 (64 bit)
Daniel James wrote: As far as I know, no-one is producing a patched kernel of this kind yet, which is why I was going down the DIY route. If all goes according to plan there should be some debs available by next month. Ok - Let me know either by the list or directly, and I'll be willing to help beta test! :) I tried Daniel James' script I can't claim credit for that, I just passed on the URL. Sorry, I assumed it was yours... I too have a Delta 1010 in my studio, and it's very well supported under Linux. I would recommend using 32-bit DeMuDi or Studio to Go for now if you want an 'out of the box' low-latency music setup. I've installed DeMuDi on the other 6gb hard drive here. Install went fine, but X wont be starting. I haven't had a chance to look at it properly yet, so once I get that working, I'll see how it runs and if it's a suitable option. :) Thanks for letting me know, though, and look foward to hearing from you for the beta test :) Cheers, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OpenOffice.org
Hi Christian, > I don't have a /lib32. Is this the Multi-Arch thing the HOWTO talks > about in the section about future plans or do they thave yet > another approach? I'm not quite sure how Ubuntu does it, but it looks like they've just added 32-bit libraries for programs that can't run without them. Perhaps one of the Ubuntu developers could give you a proper answer! Cheers Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Zero latency kernel 2.6.10 (64 bit)
Hi James, > Does anyone know where I can find a binary zero-latency kernel > 2.6.10 (for amd64 obviously..)? As far as I know, no-one is producing a patched kernel of this kind yet, which is why I was going down the DIY route. If all goes according to plan there should be some debs available by next month. > I tried Daniel James' script I can't claim credit for that, I just passed on the URL. I too have a Delta 1010 in my studio, and it's very well supported under Linux. I would recommend using 32-bit DeMuDi or Studio to Go for now if you want an 'out of the box' low-latency music setup. Cheers Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kile crash bug
kile (a nice TeX program part of KDE for those who havn't heard of it) crashes when you run the quick start wizard. I have filed a bug at kde.org http://bugs.kde.org/show_bug.cgi?id=101670 and have emailed the Debian maintainer but he says he isn't the packager for the 64 bit releases and doesn't know who is. First, has anyone else encountered this bug, and seccond, does anyone know who built and packaged the program, or where to find out? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
harddisk DMA
hi there, i have 2.6.10-9 installed on SIS chipset hardware. the SIS5513 module is loaded, but doesn't work with DMA support for my harddisks. hdparm -d1 /dev/hda tells me that this operation is not supported: filou:~# cat /proc/ide/hda/settings namevalue min max mode - --- --- acoustic0 0 254 rw address 0 0 2 rw bios_cyl65535 0 65535 rw bios_head 16 0 255 rw bios_sect 63 0 63 rw bswap 0 0 1 r current_speed 0 0 70 rw failures0 0 65535 rw init_speed 0 0 70 rw io_32bit0 0 3 rw keepsettings0 0 1 rw lun 0 0 7 rw max_failures1 0 65535 rw multcount 0 0 16 rw nice1 1 0 1 rw nowerr 0 0 1 rw number 0 0 3 rw pio_modewrite-only 0 255 w unmaskirq 0 0 1 rw using_dma 0 0 1 rw wcache 1 0 1 rw filou:~# filou:~# hdparm -d1 /dev/hda /dev/hda: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma= 0 (off) filou:~# i have no idea, weher to start searching. there is also some misterious dmesg message: PCI: Using ACPI for IRQ routing ** Routing PCI interrupts for all devices because "pci=routeirq" ** was specified. If this was required to make a driver work, ** please email the output of "lspci" to [EMAIL PROTECTED] ** so I can fix the driver. ACPI: PCI interrupt :00:02.7[C] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI interrupt :00:03.0[A] -> GSI 20 (level, low) -> IRQ 20 ACPI: PCI interrupt :00:03.1[B] -> GSI 21 (level, low) -> IRQ 21 ACPI: PCI interrupt :00:03.2[C] -> GSI 22 (level, low) -> IRQ 22 ACPI: PCI interrupt :00:03.3[D] -> GSI 23 (level, low) -> IRQ 23 ACPI: PCI interrupt :00:04.0[A] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI interrupt :00:05.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI interrupt :00:06.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI interrupt :00:07.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI interrupt :00:09.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI-DMA: Disabling IOMMU. but i don't know if this corresponds to a non working ide-dma... greetings uwe -- --- ASUS K8S-MX, 2800+ (754), 512MB, gnuLinux v2.6.x -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
