Linux-Hardware Digest #844, Volume #14 Wed, 30 May 01 02:13:05 EDT
Contents:
ide cdrw under redhat linux 7.0 ("jack")
Re: How could I make a raw copy of a disk ? ("Pavan")
Re: Scanner Epson 610U with SuSE7.1 (cash)
Re: LM-SENSORS & A7Vi-Vm ("Pavan")
Re: Via VT82C686 Sound Card ("Pavan")
----------------------------------------------------------------------------
From: "jack" <[EMAIL PROTECTED]>
Subject: ide cdrw under redhat linux 7.0
Date: Wed, 30 May 2001 05:12:53 GMT
hi,
i'm trying to setup redhat with cdrw burner. i check how to and compatible
list. it is under compatibility list. i download the binary from cdroast but
since it is ide it asked me to enable scsi emulation in kernel.
is there any easy way to configure ide cdrw under linux. cause i don't
want to go thru' all configuring kernel. the reason is i'm not advanced user
and don't want to screw up something else. if there's any solutions i really
appreciate ur help.
thanx
jack
------------------------------
From: "Pavan" <[EMAIL PROTECTED]>
Subject: Re: How could I make a raw copy of a disk ?
Date: Wed, 30 May 2001 10:49:35 +0530
>
> For my own information, edification and enjoyment; what's wrong
with
> cp -ax / /mnt/newdisk ? I use this regularly for mirroring my /
> install on a seperate device. I verify this with a find cmp
sequence
> taken from the Hard Drive Upgrade mini How To.
>
Come to think about this, it has its own advantages and disadvantages
in my opinion. Depending on how much the disk is used, cp might be
faster. Also if the partition has a large no. of small files, it is
similar to the small bs in dd and hence cp would be slow(Am I right
here?).
dd with a large block size would be a very fast sequential access of
the disk and would ideally reach the maximum data rates of the disks.
However dd will not bother about used or unused disk space.
-Pavan
------------------------------
From: cash <[EMAIL PROTECTED]>
Subject: Re: Scanner Epson 610U with SuSE7.1
Date: Tue, 29 May 2001 22:17:30 -0700
Reply-To: [EMAIL PROTECTED]
I'm trying to at least, but havn't gotten there yet. Here's what I CAN do:
/home/magreen> cat /proc/bus/usb/devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=e000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=04b8 ProdID=010c Rev= 0.01
S: Manufacturer=EPSON
S: Product=Perfection640
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
Unfortunately, when I try to scan, nothing happens. Here's what I did:
./scanimage -L
This is what shows up in the /var/log/messages file:
May 29 22:07:35 reesie kernel: Linux video capture interface: v1.00
May 29 22:07:35 reesie kernel: i2c-core.o: i2c core module
May 29 22:07:35 reesie kernel: i2c-algo-bit.o: i2c bit algorithm module
May 29 22:07:35 reesie kernel: bttv: driver version 0.7.35 loaded
May 29 22:07:35 reesie kernel: bttv: using 2 buffers with 2080k (4160k
total) for capture
May 29 22:07:35 reesie insmod: /lib/modules/2.2.16/misc/bttv.o:
init_module: Device or resource busy
May 29 22:07:35 reesie insmod: Hint: this error can be caused by incorrect
module parameters, including invalid IO or IRQ parameters
May 29 22:07:35 reesie insmod: /lib/modules/2.2.16/misc/bttv.o: insmod
char-major-81 failed
May 29 22:07:35 reesie kernel: scanner.c: open_scanner(0): Unable to access
minor data
What do I need to do?
>dmesg
Linux video capture interface: v1.00
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
bttv: driver version 0.7.35 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
Linux video capture interface: v1.00
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
bttv: driver version 0.7.35 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
Linux video capture interface: v1.00
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
bttv: driver version 0.7.35 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
Linux video capture interface: v1.00
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
bttv: driver version 0.7.35 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
Linux video capture interface: v1.00
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
bttv: driver version 0.7.35 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
scanner.c: open_scanner(0): Unable to access minor data
_______________________________________
Michael Alexander Green
[EMAIL PROTECTED]
http://www.reesie.digitalf.com/~magreen__
<
Daniel Schneider wrote:
> Hi,
>
> I've been trying to set up a USB-scanner on SuSE Linux 7.1...i think i'm
> almost there, usb started, all required modules loaded, usbview shows the
> exact data of my scanner.
> But when i start xsane, scanimage, whatever: my scanner is not recognized.
> very strange: i have two devs in /dev:
> /dev/usbscanner and /dev/usbscanner0
>
> if i use /dev/usbscanner in /etc/sane.d/epson.conf, the output of xsane
> is: xsane: nodevices available
> if i use /dev/usbscanner0 in /etc/sane.d/epson.conf, xsane hangs, only
> brute kill helps.
>
> but i know the scanner works...i had it running on RedHat7.0...
> i know about the problems with suse7.1 stated at
> http://www.freecolormanagement.com/sane/suse71.html, followed the
> step-by-step-tutorial...but it still does not work.
>
> Any help appreciated, Daniel (<-almost desperate)
> some information (i get a lot of error messages i am not able to solve):
>
> root@linux:/home/schnaarr > uname -a
> Linux linux 2.2.18 #1 Fri Jan 19 22:10:35 GMT 2001 i686 unknown
> (i tried 2.4, didn't work, too)
>
> root@linux:/home/schnaarr > lsmod
> Module Size Used by
> ...
> scanner 4768 1
> hid 11680 0 (unused) usb /dev/usbscanner
> input 2880 0 [mousedev hid]
> usb-uhci 19056 0 (unused)
> ...
> usbcore 45104 1 [hid usb-uhci]
> ...
>
>
> contents of /etc/sane.d/epson.conf:
> /usb/dev/usbscanner
>
> root@linux:/home/schnaarr > cat /proc/usb/devices
> T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 0.00
> S: Product=USB UHCI Root Hub
> S: SerialNumber=d400
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs= 1
> P: Vendor=04b8 ProdID=0103 Rev= 0.01
> S: Manufacturer=EPSON
> S: Product=Perfection610
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner
> E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
>
>
> root@linux:/home/schnaarr > cat /proc/usb/drivers
> 48- 63: usbscanner
> hid
> hub
> usbdevfs
>
> root@linux:/home/schnaarr > dmesg
>
> Buffer cache hash table entries: 262144 (order 8, 1024k)
> Page cache hash table entries: 65536 (order 6, 256k)
> Inode hash table entries: 16384 (128k), inode-max: 16384
> VFS: Diskquotas version dquot_6.4.0 initialized
> CPU: L1 I Cache: 64K L1 D Cache: 64K
> CPU: L2 Cache: 256K
> CPU: AMD Athlon(tm) Processor stepping 02
> Enabling fast FPU save and restore... done.
> Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.35a (19990819) Richard Gooch ([EMAIL PROTECTED])
> PCI: PCI BIOS revision 2.10 entry at 0xfb380, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> TCP: Hash tables configured (ehash 262144 bhash 65536)
> Initializing RT netlink socket
> Starting kswapd v 1.5
> Detected PS/2 Mouse Port.
> Serial driver version 4.27 with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ
> enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> pty: 256 Unix98 ptys configured
> Real Time Clock Driver v1.09
> RAM disk driver initialized: 16 RAM disks of 64000K size
> loop: registered device at major 7
> Uniform Multi-Platform E-IDE driver Revision: 6.30
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39
> VP_IDE: chipset revision 16
> VP_IDE: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
> hda: IBM-DJNA-351520, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: IBM-DJNA-351520, 14664MB w/430kB Cache, CHS=1869/255/63
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> LVM version 0.9 by Heinz Mauelshagen (13/11/2000)
> lvm -- Driver successfully initialized
> md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
> linear personality registered
> raid0 personality registered
> raid1 personality registered
> raid5 personality registered
> raid5: measuring checksumming speed
> raid5: MMX detected, trying high-speed MMX checksum routines
> pII_mmx : 1863.852 MB/sec
> p5_mmx : 2333.244 MB/sec
> 8regs : 1077.849 MB/sec
> 32regs : 869.442 MB/sec
> using fastest function: p5_mmx (2333.244 MB/sec)
> scsi : 0 hosts.
> scsi : detected total.
> md.c: sizeof(mdp_super_t) = 4096
> Partition check:
> hda: hda1 hda2 hda3 hda4
> RAMDISK: Compressed image found at block 0
>
Uncompressing...............................................................................done.
> autodetecting RAID arrays
> autorun ...
> ... autorun DONE.
> apm: BIOS version 1.2 Flags 0x07 (Driver version 1.13)
> VFS: Mounted root (ext2 filesystem).
> ncr53c8xx: at PCI bus 0, device 9, function 0
> ncr53c8xx: 53c810a detected with Symbios NVRAM
> ncr53c810a-0: rev 0x23 on pci bus 0 device 9 function 0 irq 11
> ncr53c810a-0: Symbios format NVRAM, ID 7, Fast-10, Parity Checking
> ncr53c810a-0: restart (scsi reset).
> scsi0 : ncr53c8xx-3.4.1-20000726
> scsi : 1 host.
> Vendor: TEAC Model: CD-ROM CD-532S Rev: 3.0A
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
> Vendor: TEAC Model: CD-R55S Rev: 1.0R
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr1 at scsi0, channel 0, id 5, lun 0
> ncr53c810a-0-<3,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 8)
> sr0: scsi3-mmc drive: 0x/0x caddy
> Uniform CD-ROM driver Revision: 3.11
> ncr53c810a-0-<5,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 8)
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> autodetecting RAID arrays
> autorun ...
> ... autorun DONE.
> Checking ReiserFS transaction log (device 03:01) ...
> Warning, log recovery starting on readonly filesystem
> Replayed 3 transactions in 4 seconds
> Using r5 hash to sort names
> please visit www.reiserfs.org for sponsor information
> ReiserFS version 3.5.28
> VFS: Mounted root (reiserfs filesystem) readonly.
> change_root: old root has d_count=1
> Trying to unmount old root ... okay
> Freeing unused kernel memory: 88k freed
> Adding Swap: 265064k swap-space (priority -1)
> Checking ReiserFS transaction log (device 03:04) ...
> Replayed 3 transactions in 4 seconds
> Using r5 hash to sort names
> ReiserFS version 3.5.28
> Checking ReiserFS transaction log (device 03:02) ...
> Using r5 hash to sort names
> ReiserFS version 3.5.28
> /dev/vmmon: Module vmmon: registered with major=10 minor=165 tag=$Name:
> build-799 $
> /dev/vmmon: Module vmmon: initialized
> parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2]
> ppuser: User-space parallel port driver
> /dev/vmnet: open called by PID 191 (vmnet-bridge)
> /dev/vmnet: hub 0 does not exist, allocating memory.
> /dev/vmnet: port on hub 0 successfully opened
> bridge-eth0: peer interface eth0 not found, will wait for it to come up
> bridge-eth0: attached
> /dev/vmnet: open called by PID 201 (vmnet-netifup)
> /dev/vmnet: hub 1 does not exist, allocating memory.
> /dev/vmnet: port on hub 1 successfully opened
> eth0: 8139too FastEthernet driver 0.9.10-2.2 Jeff Garzik
> <[EMAIL PROTECTED]>
> eth0: Linux-2.2 bug reports to Jens David <[EMAIL PROTECTED]>
> eth0: RealTek RTL8139 Fast Ethernet board found at 0xd02b4000, IRQ 10
> eth0: Chip is 'RTL-8139C' - MAC address '00:30:84:29:a2:4d'.
> bridge-eth0: found peer eth0
> bridge-eth0: up
> /dev/vmnet: open called by PID 216 (vmnet-dhcpd)
> /dev/vmnet: port on hub 1 successfully opened
> usb-uhci.c: $Revision: 1.237 $ time 22:24:29 Jan 19 2001
> usb-uhci.c: High bandwidth mode enabled
> usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 9
> usb-uhci.c: Detected 2 ports
> usb.c: new USB bus registered, assigned bus number 1
> usb.c: USB new device connect, assigned device number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> usb.c: registered new driver hid
> mice: PS/2 mouse device common for all mice
> usb.c: USB new device connect, assigned device number 2
> usb-uhci.c: ENXIO 80000280, flags 0, urb cfd76c20, burb cfd76860
> usb.c: error getting string descriptor 0 (error=-6)
> usb-uhci.c: ENXIO 80000280, flags 0, urb cfd76c20, burb cfd76860
> usb.c: error getting string descriptor 0 (error=-6)
> usb-uhci.c: ENXIO 80000280, flags 0, urb cfd76c20, burb cfd76860
> usb.c: error getting string descriptor 0 (error=-6)
> usb-uhci.c: ENXIO 80000280, flags 0, urb cfd76c20, burb cfd76860
> usb.c: error getting string descriptor 0 (error=-6)
> usb.c: USB device 2 (prod/vend 0x4b8/0x103) is not claimed by any active
> driver.
> hub.c: already running port 2 disabled by hub (EMI?), re-enabling...
> usb.c: USB disconnect on device 2
> usb.c: USB new device connect, assigned device number 2
> usb.c: USB device 2 (prod/vend 0x4b8/0x103) is not claimed by any active
> driver.
> NVRM: loading NVIDIA kernel module version 1.0-769
> pppoed uses obsolete (PF_INET,SOCK_PACKET)
> Registering PPPoE driver
> mssclampfw v1.2 (written by Marc Boucher <[EMAIL PROTECTED]>. Thanks to
> Rebel.com)
> CSLIP: code copyright 1989 Regents of the University of California
> PPP: version 2.3.7 (demand dialling)
> PPP line discipline registered.
> registered device ppp0
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
>
> ...message repeated about ten times...
>
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
>
> ...repeated again and again...
>
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
> scanner.c: open_scanner(0): Scanner device is already open
>
> ...message repeated ten times...
>
> scanner.c: open_scanner(0): Scanner device is already open
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> scanner.c: read_scanner(0): excessive NAK's received
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
>
> ...repeat...
>
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
>
> repeat
>
> Linux video capture interface: v1.00
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> bttv: driver version 0.7.35 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
> scanner.c: open_scanner(0): Scanner device is already open
>
> ...repeat...
>
> scanner.c: open_scanner(0): Scanner device is already open
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
>
> ...repeat...
>
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> usb_control/bulk_msg: timeout
> scanner.c: read_scanner(0): excessive NAK's received
>
>
>
> May 16 21:05:28 linux kernel: usb.c: new USB bus registered, assigned bus
> number
> 1
> May 16 21:05:28 linux kernel: usb.c: USB new device connect, assigned
> device num
> ber 1
> May 16 21:05:28 linux kernel: hub.c: USB hub found
> May 16 21:05:28 linux kernel: hub.c: 2 ports detected
> May 16 21:05:28 linux kernel: usb.c: registered new driver hid
> May 16 21:05:28 linux kernel: mice: PS/2 mouse device common for all mice
> May 16 21:05:28 linux kernel: usb.c: USB new device connect, assigned
> device num
> ber 2
> May 16 21:05:28 linux kernel: usb-uhci.c: ENXIO 80000280, flags 0, urb
> cfd76c20,
> burb cfd76860
> May 16 21:05:28 linux kernel: usb.c: error getting string descriptor 0
> (error=-6
> )
> May 16 21:05:28 linux kernel: usb-uhci.c: ENXIO 80000280, flags 0, urb
> cfd76c20,
> burb cfd76860
> May 16 21:05:28 linux kernel: usb.c: error getting string descriptor 0
> (error=-6
> )
> May 16 21:05:28 linux kernel: usb-uhci.c: ENXIO 80000280, flags 0, urb
> cfd76c20,
> burb cfd76860
> May 16 21:05:28 linux kernel: usb.c: error getting string descriptor 0
> (error=-6
> )
> May 16 21:05:28 linux kernel: usb-uhci.c: ENXIO 80000280, flags 0, urb
> cfd76c20,
> burb cfd76860
> May 16 21:05:28 linux kernel: usb.c: error getting string descriptor 0
> (error=-6
> )
> May 16 21:05:28 linux kernel: usb.c: USB device 2 (prod/vend 0x4b8/0x103)
> is not
> claimed by any active driver.
> May 16 21:05:28 linux kernel: hub.c: already running port 2 disabled by
> hub (EMI
> ?), re-enabling...
> May 16 21:05:28 linux kernel: usb.c: USB disconnect on device 2
> May 16 21:05:28 linux kernel: usb.c: USB new device connect, assigned
> device num
> ber 2
> May 16 21:05:28 linux kernel: usb.c: USB device 2 (prod/vend 0x4b8/0x103)
> is not
> claimed by any active driver.
> May 16 21:05:29 linux /usr/sbin/cron[381]: (CRON) STARTUP (fork ok)
> May 16 21:05:32 linux kernel: NVRM: loading NVIDIA kernel module version
> 1.0-769
> ...
>
> May 16 21:12:18 linux modprobe: modprobe: Can't locate module
> char-major-108 ...
>
> May 16 21:17:33 linux kernel: Linux video capture interface: v1.00
> May 16 21:17:33 linux kernel: i2c-core.o: i2c core module
> May 16 21:17:33 linux kernel: i2c-algo-bit.o: i2c bit algorithm module
> May 16 21:17:33 linux kernel: bttv: driver version 0.7.35 loaded
> May 16 21:17:33 linux kernel: bttv: using 2 buffers with 2080k (4160k
> total) for
> capture
> May 16 21:17:33 linux insmod: /lib/modules/2.2.18/misc/bttv.o:
> init_module: Devi
> ce or resource busy
> May 16 21:17:33 linux insmod: Hint: insmod errors can be caused by
> incorrect mod
> ule parameters, including invalid IO or IRQ parameters
> May 16 21:17:33 linux insmod: /lib/modules/2.2.18/misc/bttv.o: insmod
> char-major
> -81 failed
> ...repeaterepeatrepeat...
> ...
> May 16 21:31:58 linux kernel: usb_control/bulk_msg: timeout
> ...
> May 16 21:32:18 linux kernel: usb_control/bulk_msg: timeout
> ...
> May 16 21:32:38 linux kernel: usb_control/bulk_msg: timeout
> ...
> May 16 21:35:38 linux kernel: scanner.c: read_scanner(0): excessive NAK's
> received
>
------------------------------
From: "Pavan" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: LM-SENSORS & A7Vi-Vm
Date: Wed, 30 May 2001 10:52:58 +0530
Forgot to mention lm_sensors-2.5.5?
-Pavan
"Pavan" <[EMAIL PROTECTED]> wrote in message
news:9evm04$2ud$[EMAIL PROTECTED]...
> Hi,
>
> How do I configure lm-sensors to show the right values on a ASUS
> A7VI-VM motherboard? I find that the other A7V boards use a asus
chip
> which is to be used with the w83* driver.
>
> However sensors-detect detects a lm80 on this MB. The values
displayed
> are totally wrong. Using the via686a driver and i2c-isa, the values
> are different but wrong. The w83* driver does not work even with the
> force_a9... option.
>
> Please help, I haven't done anything to the conf file. Where do I
find
> the right configuration for this motherboard? BTW the i2c-viapro
> driver is used and it detects ( in /var/log/messages ) a via 596
chip
> instead of the 686b chip that I have.
>
> TIA,
> Pavan
>
>
------------------------------
From: "Pavan" <[EMAIL PROTECTED]>
Subject: Re: Via VT82C686 Sound Card
Date: Wed, 30 May 2001 11:04:13 +0530
> > I have a Via VT82C686 Sound Card, and Its not working in Linux.
Redhat 7.0
> > detects it, but after it detects it, it completly freezes the
system. I
> > don't know what to do. Do I need to change anything in the BIOS
like the
> > IRQ's or DMA channel?
>
> You need to enable "Sound Blaster" emulation in BIOS.
Wrong, you should not enable that. After enabling SB emulation, it
should work as a SB16 card in RH. Haven't tried this yet. However this
chip is supported directly by RH7. If you have problems, get the new
2.4 series kernel or get RH7.1
-Pavan
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
