Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting
Mailing Lists: lists.debian.org > debian-user-digest > 07 > 080432.html (Request Expert lists.debian.org Support)

debian-user-digest Digest V2007 #2270

From: <debian-user-digest-request(at)lists.debian.org>
Date: Wed Aug 29 2007 - 04:37:54 EDT


Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 2270

Today's Topics: 

  USB Hard Drive problems               [ Celejar  ]
  Re: aptitude dist-upgrade and tex de  [ "Douglas A. Tutty"  ]
  xterm won't start on AMD K6 with sto  [ Paul Scott  ]
  Re: WYSIWYG editor                    [ David Baron  ]
  Re: nvidia-glx under Debian 4.0r1     [ David Baron  ]
  Webcam in an i386 chroot (on an amd6  [ Davide Mancusi  ]
  Re: Webcam in an i386 chroot (on an   [ Davide Mancusi  ]
  Re: nvidia-glx under Debian 4.0r1     [ Florian Kulzer  ]

Date: Tue, 28 Aug 2007 23:15:26 -0400
From: Celejar <celejar@gmail.com>
To: debian-user <debian-user@lists.debian.org> Subject: USB Hard Drive problems 

Message-Id: <20070828231526.f462140e.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

I recently purchased a factory recertified Fantom Drives 120 GB USB drive. I have just begun to use it, and I'm experiencing major headaches. Every now and then (I don't see a triggering condition or chronological pattern, but I see the problem several times a day) the drive goes offline. Sometimes remounting fixes it, but at least twice (including the period after the second incident seen below in the log) it required power cycling. One of those times its status light went red; usually it stays its normal blue, including during and after the second incident below. I don't know much about HDDs; I'm including copious syslog extracts from the last couple of failures. Is this a hardware problem? Is there anything I can do? 

Aug 28 21:29:37 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 3
Aug 28 21:29:37 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:38 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:38 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 3
Aug 28 21:29:38 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:38 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:38 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 3
Aug 28 21:29:39 lizzie kernel: usb 5-7: device not accepting address 3, error -71
Aug 28 21:29:39 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 3

Do you need help?X

Aug 28 21:29:39 lizzie kernel: usb 5-7: device not accepting address 3, error -71
Aug 28 21:29:39 lizzie kernel: usb 5-7: USB disconnect, address 3
Aug 28 21:29:39 lizzie kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Aug 28 21:29:39 lizzie kernel: end_request: I/O error, dev sda, sector 124256335
Aug 28 21:29:39 lizzie kernel: Buffer I/O error on device sda1, logical block 15532034
Aug 28 21:29:39 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 21:29:39 lizzie kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Aug 28 21:29:39 lizzie kernel: end_request: I/O error, dev sda, sector 8279
Aug 28 21:29:39 lizzie kernel: Buffer I/O error on device sda1, logical block 1027
Aug 28 21:29:39 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 21:29:39 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 4
Aug 28 21:29:40 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:40 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:40 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 5
Aug 28 21:29:40 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:40 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 21:29:40 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 6
Aug 28 21:29:41 lizzie kernel: usb 5-7: device not accepting address 6, error -71
Aug 28 21:29:41 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 7
Aug 28 21:29:41 lizzie kernel: usb 5-7: device not accepting address 7, error -71
Aug 28 21:30:26 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device

Do you need more help?X

Aug 28 21:30:26 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:26 lizzie kernel: EXT3-fs error (device sda1): ext3_get_inode_loc: unable to read inode block - inode=7766021, block=15532034
Aug 28 21:30:26 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:26 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 21:30:26 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 21:30:26 lizzie kernel: EXT3-fs error (device sda1) in ext3_reserve_inode_write: IO failure
Aug 28 21:30:26 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:26 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 21:30:26 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 21:30:26 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:26 lizzie last message repeated 5 times
Aug 28 21:30:26 lizzie kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #7766021 offset 0
Aug 28 21:30:26 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:26 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 21:30:26 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 21:30:26 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:32 lizzie last message repeated 2 times
Aug 28 21:30:32 lizzie kernel: journal_bmap: journal block not found at offset 14926 on sda1
Aug 28 21:30:32 lizzie kernel: Aborting journal on device sda1.
Aug 28 21:30:32 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:32 lizzie kernel: Buffer I/O error on device sda1, logical block 1545
Aug 28 21:30:32 lizzie kernel: lost page write due to I/O error on sda1

Can we help you?X

Aug 28 21:30:44 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:44 lizzie kernel: ext3_abort called.
Aug 28 21:30:44 lizzie kernel: EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Aug 28 21:30:44 lizzie kernel: Remounting filesystem read-only
Aug 28 21:30:47 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:30:52 lizzie last message repeated 3 times
Aug 28 21:32:33 lizzie kernel: scsi 0:0:0:0: rejecting I/O to dead device
Aug 28 21:32:40 lizzie last message repeated 2 times
Aug 28 21:32:40 lizzie kernel: Buffer I/O error on device sda1, logical block 1545
Aug 28 21:32:40 lizzie kernel: lost page write due to I/O error on sda1

[snip] 

Aug 28 22:38:47 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 8
Aug 28 22:38:47 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:47 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:47 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 8
Aug 28 22:38:47 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:48 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:48 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 8
Aug 28 22:38:48 lizzie kernel: usb 5-7: device not accepting address 8, error -71
Aug 28 22:38:48 lizzie kernel: usb 5-7: reset high speed USB device using ehci_hcd and address 8
Aug 28 22:38:49 lizzie kernel: usb 5-7: device not accepting address 8, error -71
Aug 28 22:38:49 lizzie kernel: usb 5-7: USB disconnect, address 8
Aug 28 22:38:49 lizzie kernel: sd 1:0:0:0: scsi: Device offlined - not ready after error recovery

Don't know where to look next?X

Aug 28 22:38:49 lizzie kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Aug 28 22:38:49 lizzie kernel: end_request: I/O error, dev sda, sector 63007
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 7871
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: Aborting journal on device sda1.
Aug 28 22:38:49 lizzie kernel: EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: EXT3-fs error (device sda1) in ext3_dirty_inode: Journal has aborted
Aug 28 22:38:49 lizzie kernel: journal commit I/O error
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 1027
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 14254082
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 15532034
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device
Aug 28 22:38:49 lizzie kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
Aug 28 22:38:49 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device

Confused? Frustrated?X

Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device
Aug 28 22:38:49 lizzie kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
Aug 28 22:38:49 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device
Aug 28 22:38:49 lizzie kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
Aug 28 22:38:49 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device
Aug 28 22:38:49 lizzie kernel: Buffer I/O error on device sda1, logical block 0
Aug 28 22:38:49 lizzie kernel: lost page write due to I/O error on sda1
Aug 28 22:38:49 lizzie kernel: ext3_abort called.
Aug 28 22:38:49 lizzie kernel: EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Aug 28 22:38:49 lizzie kernel: Remounting filesystem read-only
Aug 28 22:38:49 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 9
Aug 28 22:38:49 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:49 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:49 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 10
Aug 28 22:38:50 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:50 lizzie kernel: usb 5-7: device descriptor read/64, error -71
Aug 28 22:38:50 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 11

Call Pantek today for Open Source Technical Support at 1-877-546-8934 - 24/7/365X

Aug 28 22:38:50 lizzie kernel: usb 5-7: device not accepting address 11, error -71
Aug 28 22:38:50 lizzie kernel: usb 5-7: new high speed USB device using ehci_hcd and address 12
Aug 28 22:38:51 lizzie kernel: usb 5-7: device not accepting address 12, error -71
Can't find what you're looking for?X

[snip] 

Aug 28 22:39:27 lizzie kernel: scsi 1:0:0:0: rejecting I/O to dead device
Aug 28 22:39:50 lizzie last message repeated 4 times
Aug 28 22:51:19 lizzie -- MARK --

Celejar 

--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator

Date: Wed, 29 Aug 2007 03:45:27 +0000 From: "Douglas A. Tutty" <dtutty@porchlight.ca> To: debian-user@lists.debian.org Subject: Re: aptitude dist-upgrade and tex dependencies Message-ID: <20070829034527.GA12340@titan.hooton> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Aug 27, 2007 at 08:38:13PM -0700, Daniel Burrows wrote:
> I don't know how the TeX team are managing their transition offhand.
> A start would be to figure out which packages are forcing the upgrade of
> tetex-extra -- you could find this out by, e.g., going into the
> interactive interface, holding tetex-extra back after the upgrade
> (manually), and then seeing what breaks.
>
Or just go to the interactive mode, go to tetex-extra, and look at what depends on it. Select those in turn and see if they depend on only tetex-extra or if they will also select texlive. Eventually, you'll find out exactly what is specific to tetex-extra and you can find replacments. E.g. instead of latex2html look at tex4ht. Doug.

Date: Wed, 29 Aug 2007 00:33:50 -0400 From: Mark Grieveson <dg135@torfree.net> To: debian-user@lists.debian.org Subject: Re: WYSIWYG editor Message-ID: <20070829003350.75d1d3a9@localhost> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Tue, 28 Aug 2007 21:13:12 +0000 (UTC) debian-user-digest-request@lists.debian.org wrote:
> > What do you recommend as a good, practical WYSIWYG editor for
> > creating simple web pages, with mostly text, some graphics and pdf,
> > for debian Lenny please? Thanks.
> >
> > --
> > Regards,
Iceape Composer is okay. A lot of people like Nvu (available in source for Linux at nvu.com). Mark

Date: Tue, 28 Aug 2007 21:22:13 -0700 From: Paul Scott <waterhorse@ultrasw.com> To: Debian User <debian-user@lists.debian.org> Subject: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel Message-ID: <46D4F475.7090007@ultrasw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Laptop with AMD K6 running Debian sid xterm works w/ stock 2.6.17-2-486 with stock 2.6.22-1-486 attempting to start xterm gives: xterm: Error 32, errno 2: No such file or directory Reason: get_pty: not enough ptys I have upgraded almost anything that needed it that would have come after the 2.6.17-2-486 kernels. Any of that upgrading may have caused the xterm problem. TIA for any more ideas. Paul Scott

Date: Wed, 29 Aug 2007 09:24:45 +0300 From: David Baron <d_baron@012.net.il> To: debian-user@lists.debian.org Subject: Re: WYSIWYG editor Message-id: <200708290924.45734.d_baron@012.net.il> Content-type: text/plain; charset=iso-8859-15 Content-transfer-encoding: quoted-printable Content-disposition: inline
> Actually WYSIWYG is VERY BAD for web page creation. People can resize the=
ir
> windows etc - and then what? =A0All your WYSIWYG has gone to waste. In
> addition your WYSIWYG is probably not even rendering the same as your
> favorite browsers.
>
> As annoying as it may be at the start, the best way is probably to edit
> with a text editor and have a browser (or several browsers) rendering the
> file.
Yup. I had a short-lived job once cutting and pasting various entries into= =20 pre-existing web pages. They insisted upon Dreamweaver. Then the stuff simp= ly=20 looked awful or out of place in the browser. Whatever tool one uses (Nvu is a nice opensource tool!), one MUST test page= s,=20 their scripts and forms and all, in several browsers. IE, Firefox/Mozilla=20 varients, Opera, Dillo, Konqueror, etc. It is surprizing after all the=20 development that has gone into these things that no two work the same and n= o=20 one works 100% with the javascript or whatever. Pain in the butt.

Date: Wed, 29 Aug 2007 09:28:15 +0300 From: David Baron <d_baron@012.net.il> To: debian-user@lists.debian.org Subject: Re: nvidia-glx under Debian 4.0r1 Message-id: <200708290928.15889.d_baron@012.net.il> Content-type: text/plain; charset=iso-8859-15 Content-transfer-encoding: 7BIT Content-disposition: inline
> Finally, do not use nvidia's own installer since it overwrites existing
> debian files on your system and will eventually make a hash of it.
1. Nvidia's installer can be run with options to avoid this problem. If you do not do it thus, every time you upgrade xorg, you need to check the /usr/lib/xorg/modules/extenstions/libglx.so to make sure it points to nvidia's (libglx.so.1.0.####). A pain but not the end of the world. 2. I found I got twice the frame rate with Nvidia's! Why? Should be same or similar code. 3. If your sound card is too old to be supported by the latest-and-greatest drivers, you MUST use the appropriate Nvidia version installer.

Date: Wed, 29 Aug 2007 09:24:49 +0200 From: Davide Mancusi <arekfu@gmail.com> To: Debian User <debian-user@lists.debian.org> Subject: Webcam in an i386 chroot (on an amd64) Message-ID: <46D51F41.3010709@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I recently upgraded my system to amd64 and now I am trying to set up an i386 jail for those programs that do not run natively on amd64. I want to use my webcam, which works well outside the chroot; however, 32-bit programs do not manage to access the device. Examples of error messages: $ schroot -p xawtv I: [sid32-8d1fa3f9-ee58-4f25-b3e6-5453ba4d40c3 chroot] Running command: "xawtv" This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.21-amd64-bootsplash) xinerama 0: 1152x864+0+0 /dev/video0 [v4l]: ioctl VIDIOCGCAP: Invalid argument no video grabber device available $ schroot -p camorama [Pop-up window: Could not connect to video device. Please check connection] $ schroot -p motion I: [sid32-9c74ac33-34ee-4ec6-b1f3-e448cc3da0e2 chroot] Running command: "motion" [0] Processing thread 0 - config file /etc/motion/motion.conf [1] Thread is from /etc/motion/motion.conf [1] Thread started [1] ioctl (VIDIOCGCAP): Invalid argument [1] Capture error calling vid_start [1] Thread finishing... I have tried to STFW, but no luck. Any suggestion? Davide -- A tautology is a thing which is tautological. -- Time flies like an arrow. Fruit flies like a banana.

Do you need help?X

Date: Wed, 29 Aug 2007 09:38:31 +0200 From: Davide Mancusi <arekfu@gmail.com> To: Debian User <debian-user@lists.debian.org> Subject: Re: Webcam in an i386 chroot (on an amd64) Message-ID: <46D52277.1080405@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Davide Mancusi ha scritto:
> I recently upgraded my system to amd64 and now I am trying to set up an
> i386 jail for those programs that do not run natively on amd64. I want
> to use my webcam, which works well outside the chroot; however, 32-bit
> programs do not manage to access the device.
>
> Examples of error messages:
> $ schroot -p xawtv
> I: [sid32-8d1fa3f9-ee58-4f25-b3e6-5453ba4d40c3 chroot] Running command:
> "xawtv"
> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.21-amd64-bootsplash)
> xinerama 0: 1152x864+0+0
> /dev/video0 [v4l]: ioctl VIDIOCGCAP: Invalid argument
> no video grabber device available
>
> $ schroot -p camorama
> [Pop-up window: Could not connect to video device. Please check connection]
>
> $ schroot -p motion
> I: [sid32-9c74ac33-34ee-4ec6-b1f3-e448cc3da0e2 chroot] Running command:
> "motion"
> [0] Processing thread 0 - config file /etc/motion/motion.conf
> [1] Thread is from /etc/motion/motion.conf
> [1] Thread started
> [1] ioctl (VIDIOCGCAP): Invalid argument
> [1] Capture error calling vid_start
> [1] Thread finishing...
>
> I have tried to STFW, but no luck. Any suggestion?
>
> Davide
>
Maybe the following info could be more useful. Compare the output of the following commands: (on amd64) $ v4lctl -v2 webcam ~/prova.jpg Xvideo: 1 adaptors available. Xvideo: ATI Radeon Video Overlay: input image, ports 115-115 Xvideo: no usable video port found vid-open: trying: v4l2-old... vid-open: failed: v4l2-old vid-open: trying: v4l2... ioctl: VIDIOC_QUERYCAP(driver="";card="";bus_info="";version=0.0.0;capabilities=0x0 []): Unknown error 515 vid-open: failed: v4l2 vid-open: trying: v4l... v4l: open: /dev/video0 (Logitech QuickCam USB) capabilities: capture size : 160x120 => 324x248 channels: 1 ioctl: VIDIOCGCHAN(channel=0;name="Camera";tuners=0;flags=0x0 [];type=CAMERA;norm=0): ok Camera: 0 camera audios : 0 ioctl: VIDIOCSCHAN(channel=0;name="Camera";tuners=0;flags=0x0 [];type=CAMERA;norm=0): ok PALioctl: VIDIOCSCHAN(channel=0;name="Camera";tuners=0;flags=0x0 [];type=CAMERA;norm=1): ok NTSCioctl: VIDIOCSCHAN(channel=0;name="Camera";tuners=0;flags=0x0 [];type=CAMERA;norm=2): ok SECAMioctl: VIDIOCSCHAN(channel=0;name="Camera";tuners=0;flags=0x0 [];type=CAMERA;norm=3): ok AUTOioctl: VIDIOCSCHAN(channel=0;name="Camera";tuners=0;flags=0x0 [];type=CAMERA;norm=0): ok ioctl: VIDIOCGFBUF(base=(nil);height=0;width=0;depth=0;bytesperline=0): ok fbuffer : base=0x(nil) size=0x0 depth=0 bpl=0 ioctl: VIDIOCGPICT(brightness=32768;hue=32768;colour=32768;contrast=32768;whiteness=32768;depth=24;palette=RGB24): ok picture : brightness=32768 hue=32768 colour=32768 contrast=32768 picture : whiteness=32768 depth=24 palette=rgb24 ioctl: VIDIOCGMBUF(size=321408;frames=1;offsets=0): ok mbuf: size=321408 frames=1 v4l: using mapped buffers for capture vid-open: ok: v4l freq: reading /usr/share/xawtv/Index.map ioctl: VIDIOCGCHAN(channel=0;name="Camera";tuners=0;flags=0x0 [];type=CAMERA;norm=0): ok ioctl: VIDIOCGPICT(brightness=32768;hue=32768;colour=32768;contrast=32768;whiteness=32768;depth=24;palette=RGB24): ok ioctl: VIDIOCGPICT(brightness=32768;hue=32768;colour=32768;contrast=32768;whiteness=32768;depth=24;palette=RGB24): ok ioctl: VIDIOCGPICT(brightness=32768;hue=32768;colour=32768;contrast=32768;whiteness=32768;depth=24;palette=RGB24): ok ioctl: VIDIOCGPICT(brightness=32768;hue=32768;colour=32768;contrast=32768;whiteness=32768;depth=24;palette=RGB24): ok cmd: "webcam" "/home/davide/prova.jpg" v4l: setformat ioctl: VIDIOCGCAP(name="Logitech QuickCam USB";type=0x1 [CAPTURE];channels=1;audios=0;maxwidth=324;maxheight=248;minwidth=160;minheight=120): ok v4l: capture probe 24 bit TrueColor (BE: rgb)... failed setformat: 24 bit TrueColor (BE: rgb) (0x0): failed v4l: setformat ioctl: VIDIOCGCAP(name="Logitech QuickCam USB";type=0x1 [CAPTURE];channels=1;audios=0;maxwidth=324;maxheight=248;minwidth=160;minheight=120): ok v4l: capture probe 24 bit TrueColor (LE: bgr)... ioctl: VIDIOCMCAPTURE(frame=0;height=120;width=160;format=4): ok ioctl: VIDIOCSYNC(int=0): ok ok setformat: 24 bit TrueColor (LE: bgr) (0x0): ok v4l: setformat ioctl: VIDIOCGCAP(name="Logitech QuickCam USB";type=0x1 [CAPTURE];channels=1;audios=0;maxwidth=324;maxheight=248;minwidth=160;minheight=120): ok v4l: getimage ioctl: VIDIOCMCAPTURE(frame=0;height=0;width=0;format=4): Invalid argument v4l: close (on i386) $ schroot -p -- v4lctl -v2 webcam ~/prova.jpg I: [sid32-25de803f-d813-4394-b7ae-35dc3b557e1a chroot] Running command: "v4lctl -v2 webcam /home/davide/prova.jpg" Xvideo: 1 adaptors available. Xvideo: ATI Radeon Video Overlay: input image, ports 115-115 Xvideo: no usable video port found vid-open: trying: v4l2-old... vid-open: failed: v4l2-old vid-open: trying: v4l2... ioctl: VIDIOC_QUERYCAP(driver="";card="";bus_info="";version=0.0.0;capabilities= 0x0 []): Invalid argument vid-open: failed: v4l2 vid-open: trying: v4l... vid-open: failed: v4l no grabber device available Davide -- A tautology is a thing which is tautological. -- Time flies like an arrow. Fruit flies like a banana.

Date: Wed, 29 Aug 2007 09:21:45 +0200 From: Florian Kulzer <florian.kulzer+debian@icfo.es> To: debian-user@lists.debian.org Subject: Re: nvidia-glx under Debian 4.0r1 Message-ID: <20070829072144.GA6192@localhost> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Aug 28, 2007 at 21:44:11 +0200, Bart wrote:
> I've installed Debian 4.0r1 and now I want 3D support for my Nvidia
> graphics card.
>
> I'm following instructions as can be found on
> http://wiki.debian.org/NvidiaGraphicsDrivers
>
> I can install the nvidia-kernel-sources, but not the nvidia-glx package.
> The error given is:
>
> The following packages have unmet dependencies:
> nvidia-glx: Depends: libc6 (>= 2.5-5) but 2.3.6.ds1-13etch2 is to be
> installed
>
> Is there a way to solve this?
You are trying to install the nvidia-glx package from Sid (a.k.a. "unstable", the "bleeding edge, may break at any time" branch of Debian.) You have to install the 4.0r1 (Etch, "stable") version of the package; this one depends on the proper version of libc6. This is probably due to a misconfiguration of your package manager. Please post the content of the following two files: /etc/apt/sources.list /etc/apt/preferences (The second file might not exist on your system; this is OK.) I would also like to see the output that you get from the following command: apt-cache policy nvidia-glx -- Regards, | http://users.icfo.es/Florian.Kulzer Florian |

Date: Wed, 29 Aug 2007 09:57:22 +0200 From: Lorenzo Bettini <bettini@dsi.unifi.it> To: Debian User Mailing List <debian-user@lists.debian.org> Subject: Re: capture real audio stream Message-ID: <46D526E2.70604@dsi.unifi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cothrige wrote:
> This is pretty easy if you have either mplayer or audacity installed.
> If you happen to be playing from BBC 7 it is particularly easy, and all
> you have to do is right click on the listen link and save the ram file
> to your drive. Then you just read it as it is plain text, and inside
> you will find something like:
>
> rtsp://rmv8.bbc.net.uk/bbc7/0930_sun.ra?BBC-UID=34f67dd2ff9daa4baac9cd5c20f0b659244a9c75a07060437bfa8149d4698951&SSO2-UID=
>
I'm trying with this one http://www.bbc.co.uk/radio2/musicclub/events_andrewlloydwebber.shtml and can't find such links, not even with Page Info (as suggested by Joachim); could it be they changed something in their site?
>
> BTW, if all of that fails for some reason then you can always open
> audacity (before the audio player to make sure your sound card is
> available for recording), adjust your input to volume and set the volume
> levels. Then you can open the browser and start the player, and begin
> the recording in audacity. This will record the stream as a wav as
> well, though if your signal drops out you will have to clean up any
> silent patches in the file. The mplayer way is much, much better as it
> will automatically correct any failures in the feed and so the resulting
> file will have no blank patches in it, so I really would recommend that
> way first.
I'll also try with audacity, but I'd like to use mplayer as you suggest... thanks in advance Lorenzo -- Lorenzo Bettini, PhD in Computer Science, DSI, Univ. di Firenze ICQ# lbetto, 16080134 (GNU/Linux User # 158233) HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com http://www.myspace.com/supertrouperabba BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com http://www.gnu.org/software/src-highlite http://www.gnu.org/software/gengetopt http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

Date: Wed, 29 Aug 2007 07:37:17 -0000 From: "David A." <achoice@gmail.com> To: debian-user@lists.debian.org Subject: (solved) Re: new drive = new install? Message-ID: <1188373037.823963.171410@k79g2000hse.googlegroups.com> Content-Type: text/plain; charset="us-ascii"
> > What is common practice when migrating a system from one drive to
> > another. Should I reinstall from scratch or partition the new drive
> > and "copy everything" from the old one?
>
> Reinstallation is not necessary. There are plenty of HOWTOs available,
> one being <http://tldp.org/HOWTO/Hard-Disk-Upgrade/index.html>.
Thanx! I managed to get the work done. The article is 7 years old but it lays out the main line. Something missing in the instructions was that the "-p" flag should be used in the "cp"-command to preserve rights. And I use grub, not lilo. But a simple "grub-install", at least on my debian, did the trick to set up grub on the new disk. I'm supprised the transfer to a new disk was so painless. I even stepped up to ext3 on the new drive. thanx, david. End of debian-user-digest Digest V2007 Issue #2270 ************************************************** Received on Wed Aug 29 04:32:09 2007

This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 07:54:16 EDT

Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library