December 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Kernel Sound Module Problem
by Stephen P. Molnar 10 Dec '09

10 Dec '09

OpenSuSSE 11.2 on AMD 64 bit CPU. I am having a problem installing a new, bare bones, sound card. Yast identifies it as a Solo-1 Audio Adapter, as does Hardware Information. Unfortunately, when I attempt to configure the sound card I get an error message: "The kernel module snd-es1938 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters." I installed the default kernel. Oh yes, I get a brief burst of white noise from my speakers when the system is booten and shut down. Assistance will be much appreciated. Thanks in advance. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Amarok 2.2.1. Random track playing does not works
by Alexander R 10 Dec '09

10 Dec '09

OpenSUSE 11.2 x86_64 KDE 4.3.4 (KDE 4.3.4) "release 2" from OBS Amarok 2.2.1 release 48.1 ~/.kde4/share/config> cat amarokrc [General Options] Last Dynamic Mode=Случайный Lock Layout=false Random Mode=Tracks Repeat=Playlist Show Splashscreen=false have anybody like this symptoms? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] mkdir: cannot create directory `/dev/shm/sysconfig/xenbridges': No such file or directory
by Yury A. Buldakov 10 Dec '09

10 Dec '09

Hi all, After updating my box from 11.1 to 11.2 I've faced next messages during xend start: mkdir: cannot create directory `/dev/shm/sysconfig/xenbridges': No such file or directory I am also experiencing problems with network setup inside of xen domU, but currently not sure if these two related. Any ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Sound problem
by Koenraad Lelong 10 Dec '09

10 Dec '09

Hi, Last week I installed OS 11.2 64bit. One of the problems is my sound-card : intel HD audio, with an ALC883 codec. I configured the model to 6stack-dig because this is what I see : 6 jack's and I have an spdif output. When I run speaker-test -c4 or -c6 or -c8, I only get sound on my front speakers (I have 4 speakers). What am I doing wrong ? When I enable surround, I do get sound from my rear speakers, but since I'm playing digital audio (mp3 or wav) I'm not sure if it's really working. What is the best way to test the audio-system, if it's not speaker-test ? Thanks for any input. -- Met vriendelijke groeten, Koenraad Lelong -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3

[opensuse] HP leaks slides with details on Radeon HD 5000-series GPUs
by Fred A. Miller 10 Dec '09

10 Dec '09

'Bet there's NO Linux support or if there is, it stinks!! Fred http://blogs.zdnet.com/gadgetreviews/?p=9966&tag=nl.e539 -- SOCIALISM is a philosophy of failure, the creed of ignorance and the gospel of envy. Its inherent virtue is the equal sharing of misery. -Winston Churchill -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] OT: does anyone here use Eudora on Win?
by Doug McGarrett 09 Dec '09

09 Dec '09

Hello all: I made a very bad decision to install Win 7 on the M/S machine. In spite of a program that was supposed to save my files and setting, everything was gone. When I reinstalled Eudora, I could not remember how to set the initial inputs--I can send but not receive mail. Help! (I sure wish there was a list like this for Windows, but I have not found one.) Oh, Win 7 has no mail program at all. I'm using Thunderbird at the moment. Does anyone know how to change the columns in Thunderbird so that the incoming sender is on the left, and the subject is on the right? Like KMail or Eudora? I could live with that. If you are running Windows, I definitely don't recommend the latest crap from M/S. Not only don't you lose all your old stuff, a lot of it cannot be reinstalled--WordPerfect is one of them. (OO seems to work.) ProgeCad (an AutoCad clone) seems to be another. Sorry for this OT note, but I don't know who else to ask. I am retired, and have no IT guys to question. Thanx--doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4

[opensuse] Understanding YaST2 Bootloader setup
by Marc Chamberlin 09 Dec '09

09 Dec '09

Well I am totally confused about using YaST2 to setup the bootloader, and no amount of reading documentation or searching the internet has allowed me to grok the underlying model of how this works... I am not looking for a cookbook set of instructions (which I find all over the place) BUT some clarification of terminology and what really is going on when I select various options. I have a system with multiple versions of SuSE installed on various different disk drives. I am using GRUB. In the YaST module for setting up the boot loader, there is a panel titled Boot Loader Installation and within that panel I am allowed to choose between one (or more) boot loader locations and this is where I am confused. The Help menu does not help either, just makes things even more confusing! So here are my questions - 1. The first choice offers me the option to Boot from Boot Partition. I cannot find a definition of what a "Boot Partition" is exactly, but my guess is that this is a partition that I will set fstab up to mount as /boot Is that correct? If so, (and I would argue that this is a bad way to name and describe it) why would I want to create a partition just for /boot? What would be the advantage and disadvantage of doing so. It seems to me that in an environment with multiple operating systems or versions of the same OS, that this might be a incredibly dangerous thing to do.. If a later version of an OS or GRUB is installed and wants to change, add, delete or modify files or the structure of files within this area, then that could break other or earlier versions of an OS, which is also dependent upon a common boot partition. Or is the thinking behind this option, to have each OS have its own boot partition? Is so why would that be an advantage? 2. The second choice is Boot from Extended Partition. I can find very little documentation on this feature and it somewhat baffles me. I am again guessing that this has something to do with installing an OS in an extended partition, but why should I have to explicitly specify that I am doing so? What is different about this option, that is not covered when either Boot From Boot Partition or Boot From Root Partition is chosen? If the Boot Partition or the Root Partition is in an extended partition why can't YaST simply figure that out and do what ever is necessary to support it? Or perhaps (and just a wild guess) does this have more to do with loading the OS from and extended partition and nothing to do with where the bootloader code actually exists? What does booting from an Extended Partition REALLY mean? 3. The third choice is Boot from Master Boot Record. While I think I understand the basic idea of the Master Boot Record, a couple of questions regarding it have come to my mind. First, the Help menu states that if one is going to have multiple OS's on ones system, then this method should not be used (not recommended) Well.... I have been using this method, and it seems to work OK. I use this method only because that apparently is the default method chosen by the SuSE installation process. This poor user would assume that if the installation process has the ability to detect if multiple operating systems are already installed, then the installation process would be smart enough to decide whether a boot from a MBR would be acceptable or not... So why is this not the recommended method for systems with multiple OS's? My second question regarding using the MBR (may in part answer the above question) comes from my reading about it. My understanding of the MBR is that it is located in the first sector of a disk drive. I also understand (and please correct me if I am wrong on this) is that on a system with multiple drives, the BIOS will choose the "first" drive to boot from it's MBR. I also read that this "order" of drives may change from one OS to another, which stunned me but then I have no idea how the BIOS works or how drive order/labels are assigned.. And indeed I discovered, (much to my dismay) that this order apparently did change between openSuSE11.0 and 11.2. Or to state what I discovered more correctly, the device referenced as /dev/sda1 on my openSuSE11.0 system is NOT the same device referenced as /dev/sda1 under openSuSE11.2 (and was I ever surprised and confused by this!!!) So if there is this sort of instability in drive order and name associations, is this why using the MBR is not recommended? And why is the SuSE installation process choosing to use this method by default, when multiple OS's are detected? I am lost on this one! The fourth choice is to Boot from Root Partition and again I am guessing that this really means to boot from the partition that I will configure fstab to mount as / Correct? If I choose this option, the Help states that I should select "Set active Flag in Partition Table for Boot Partition" Why??? Do I have to have a separate Boot Partition in order to use this Boot from Root Partition option? It seems to me that I should be setting an active flag in the Partition Table for the Root Partition, not for a Boot Partition. But then I see there is no such option in the Boot Loader Options, so is this an oversight?. And why don't the Help instructions tell me to set the active flag for the Boot Partition if I am going to use a Boot Partition? If I am going to choose to boot from the Boot Partition do I also have to explicitly tell YaST to Write Generic Boot Code to MBR, or does YaST assume this, and write something special to the MBR to work with the info in the Boot Partition? What does YaST set up if I have my boot loader in a Boot Partition and I select Write Generic Boot Code to MBR? Conversely, if I am choosing to boot from a Root Partition, then it seems I MUST choose to Write Generic Boot Code to MBR. When and why wouldn't I? Unless some sort of bootloader is written to the MBR, it does not seem possible that a system would boot, so why have this as an option under this condition, or does YaST simply assume that a boot loader, of some kind, already exists in the MBR? Shouldn't YaST at least warn me that a boot loader was not completely set up, in case I forget to tell it to Write Generic Boot Code to the MBR? Or perhaps, shouldn't I be forced to either tell YaST to Write Generic Boot Code to the MBR, or that there already is a valid bootloader there and I know this for a fact and YaST does not have to worry about it? This seems like a dangerous user trap to me, but again my ability to grok the underlying model has failed me, so perhaps I am missing something obvious. Finally, and this indicates that I must have a fundamental misunderstanding of the underlying model for boot loader locations, I noted that YaST2 allows me to select multiple Boot Loader Locations. What does it mean to check more than one location? How does that work, and why would I choose more than one location? Anywise I hope some nice guru will clarify these questions for me... I am trying to understand all this in order to more fully understand some other problems I seem to be having with the boot process. If there is a good description of the model for the boot load process, I would appreciate a pointer... I have already read most of what I could find in the SuSE docs, the GRUB website, and info manual and none of it helped me gain a deeper understanding of how the boot loaders really work and what all these location options mean.. Thanks in advance.... Marc.. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] Re: Understanding YaST2 Bootloader setup
by jdd-gmane 09 Dec '09

09 Dec '09

Le 09/12/2009 19:10, Felix Miata a écrit : > The reason for distinguishing between "primary" and "logical" partitions > applies entirely to the boot process that's not true. In fact I had the same thinking for several years. But as the author of the Partition Rescue HOWTO, I was made aware by a reader that logical partitions have to store the Inodes/fat somewhere and this somewhere is the first sector of the partition. So very soon after the logical partition creation some bits are written to the drive on theses sectors. If you happen to have data there, you can lose things. This is important when one have lost the partition table and don't have the exact data on paper. Using guesses can destroy some bits of data. there is no similar problem for primaries, as they data is in the first disk sector, never used for storing data jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Yast2/Firewall. Is it possible to MASQUERADE from Internal to External zone?
by Alexander R 09 Dec '09

09 Dec '09

My system is: - OpenSUSE 11.1 x86_64 (all package is by default from OSS repo) I've SERVER1 with 4 ethernet interfaces that is in bonding mode: eth0,eth1=bond0; eth2,eth3=bond1. Bonding mode is "Active-Standby" bond0 - Internal zone bond1 - External zone bond1:111 (192.168.0.93/24) - additional IP on interface my network map is: HOST11(10.1.1.60/24)------bond0(10.1.1.174/24)_SERVER1_bond1(192.168.0.92/24)------....HOST21(192.168.0.12/24) and HOST22(192.168.0.2/24) My issue: I've configured masquerading from HOST21 to HOST11:5901 tcp port, through SERVER1_bond1:5901 and it's works fine. ok. But when I try to masquerade from HOST11 to HOST22:25 tcp port, through SERVER1_bond0:2525 (for example) tcp port, it does not work. While I try to connect from HOST11 to SERVER1-bond0:2525, I see in /var/log/firewall only this line: Dec 9 17:56:51 SERVER1 kernel: SFW2-INint-ACC-ALL IN=bond0 OUT= MAC=00:1e:0b:70:06:36:00:50:56:80:2a:10:08:00 SRC=10.1.1.60 DST=10.1.1.174 LEN=60 TOS=0x10 PREC=0x00 TTL=64 ID=12 DF PROTO=TCP SPT=38336 DPT=2525 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080AA96B58700000000001030302) Any suggestions? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Nasty USB kernel error causes usb drive disconnect and disconnect of ALL mounted smb network shares
by David C. Rankin 09 Dec '09

09 Dec '09

Guys, I have had a strange occurrence with a USB drive attached to my computer. I don't know if this is due to the new ext4 format on the usb drive or a kernel error affecting the usb subsystem. The usb drive I have has another install on it with / as ext4 and /home still ext3 per the 11.2 setup defaults. When I connect the drive to 11.2 the connection and automount work like they are supposed to. However, anywhere from 1 - 30 minutes later, a kernel error occurs that knocks the drive and all partitions off-line AND disconnects all smb mounted drives. Here is a snippet of the log entries. Full log at: http://www.3111skyline.com/download/openSUSE_bugs/112/kernel/kernel-error-u… Nov 19 15:31:42 alchemy kernel: [75027.512129] ------------[ cut here ]------------ Nov 19 15:31:42 alchemy kernel: [75027.512186] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.31.5/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x67/0x90() Nov 19 15:31:42 alchemy kernel: [75027.512216] Hardware name: Satellite P205D Nov 19 15:31:42 alchemy kernel: [75027.512230] inotify closing but id=0 for entry=ffff8800d20a1898 in group=ffff880118d81780 still in idr. Probably leaking memory Nov 19 15:31:42 alchemy kernel: [75027.512254] Modules linked in: st ide_gd_mod ide_cd_mod nls_utf8 cifs ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit cryptd crypto_wq aes_x86_64 aes_generic snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd af_packet radeon drm ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter cpufreq_conservative cpufreq_userspace ip6table_mangle cpufreq_powersave powernow_k8 nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables fuse loop dm_mod arc4 ecb cryptomgr aead pcompress crypto_blkcipher pcmcia crypto_hash snd_hda_codec_realtek crypto_algapi snd_hda_intel snd_hda_codec sdhci_pci ath5k mac80211 sr_mod snd_hwdep amd64_edac_mod tifm_7xx1 yenta_socket ohci1394 rsrc_nonstatic snd_pcm edac_core k8temp pcspkr joydev tifm_core sg cdrom ath sdhci battery mmc_core ieee1394 video pcmcia_core ac shpchp pci_hotplug i2c_piix4 cfg80211 button rfkill snd_timer snd snd_page_alloc r8169 ext Nov 19 15:31:42 alchemy kernel: 4 jbd2 crc16 fan processor ide_pci_generic atiixp ide_core ata_generic pata_atiixp thermal thermal_sys [last unloaded: preloadtrace] Nov 19 15:31:42 alchemy kernel: [75027.512770] Pid: 7787, comm: kded Not tainted 2.6.31.5-0.1-desktop #1 Nov 19 15:31:42 alchemy kernel: [75027.512786] Call Trace: Nov 19 15:31:42 alchemy kernel: [75027.512828] [<ffffffff81011a19>] try_stack_unwind+0x189/0x1b0 Nov 19 15:31:42 alchemy kernel: [75027.512854] [<ffffffff8101025d>] dump_trace+0xad/0x3a0 Nov 19 15:31:42 alchemy kernel: [75027.512877] [<ffffffff81011524>] show_trace_log_lvl+0x64/0x90 Nov 19 15:31:42 alchemy kernel: [75027.512900] [<ffffffff81011573>] show_trace+0x23/0x40 Nov 19 15:31:42 alchemy kernel: [75027.512925] [<ffffffff81551ee2>] dump_stack+0x81/0x9e Nov 19 15:31:42 alchemy kernel: [75027.512950] [<ffffffff8106aec0>] warn_slowpath_common+0x80/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.512973] [<ffffffff8106af9b>] warn_slowpath_fmt+0x4b/0x70 Nov 19 15:31:42 alchemy kernel: [75027.512995] [<ffffffff8118b9b7>] idr_callback+0x67/0x90 Nov 19 15:31:42 alchemy kernel: [75027.513056] [<ffffffff81287b2c>] idr_for_each+0x9c/0x110 Nov 19 15:31:42 alchemy kernel: [75027.513089] [<ffffffff8118b921>] inotify_free_group_priv+0x31/0x60 Nov 19 15:31:42 alchemy kernel: [75027.513121] [<ffffffff81188e22>] fsnotify_final_destroy_group+0x32/0x60 Nov 19 15:31:42 alchemy kernel: [75027.513152] [<ffffffff81188f88>] fsnotify_put_group+0xb8/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.513183] [<ffffffff8118bcbd>] inotify_release+0x3d/0x70 Nov 19 15:31:42 alchemy kernel: [75027.513217] [<ffffffff8114dbc9>] __fput+0xe9/0x220 Nov 19 15:31:42 alchemy kernel: [75027.513246] [<ffffffff8114dd28>] fput+0x28/0x50 Nov 19 15:31:42 alchemy kernel: [75027.513283] [<ffffffff81149547>] filp_close+0x67/0xb0 Nov 19 15:31:42 alchemy kernel: [75027.513314] [<ffffffff8106d907>] put_files_struct+0x87/0x100 Nov 19 15:31:42 alchemy kernel: [75027.513345] [<ffffffff8106d9dc>] exit_files+0x5c/0x80 Nov 19 15:31:42 alchemy kernel: [75027.513375] [<ffffffff8106f41e>] do_exit+0x17e/0x3c0 Nov 19 15:31:42 alchemy kernel: [75027.513404] [<ffffffff8106f6b8>] do_group_exit+0x58/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.513435] [<ffffffff8106f755>] sys_exit_group+0x25/0x40 Nov 19 15:31:42 alchemy kernel: [75027.513466] [<ffffffff8100c682>] system_call_fastpath+0x16/0x1b Nov 19 15:31:42 alchemy kernel: [75027.513508] [<00007fc214ba3c08>] 0x7fc214ba3c08 Nov 19 15:31:42 alchemy kernel: [75027.513528] ---[ end trace 036570030a664eac ]--- Nov 19 15:31:42 alchemy kernel: [75027.513549] entry->group=(null) inode=(null) wd=4096 <snip> Nov 19 18:20:25 alchemy laptop-mode: Adjusting 2.6 kernel parameters to disable laptop mode. Nov 19 18:20:25 alchemy laptop-mode: /sys/kernel/debug not found in PARTITIONS. Nov 19 18:20:25 alchemy laptop-mode: /sys/kernel/security not found in PARTITIONS. Nov 19 18:20:44 alchemy kernel: [10092.013951] ISO 9660 Extensions: Microsoft Joliet Level 3 Nov 19 18:20:44 alchemy kernel: [10092.157800] ISO 9660 Extensions: RRIP_1991A Nov 19 20:37:26 alchemy kernel: [18293.804949] lp: driver loaded but no devices found Nov 19 20:37:26 alchemy kernel: [18293.900397] ppdev: user-space parallel port driver Nov 19 23:12:47 alchemy kernel: [27614.916307] ath5k phy0: unsupported jumbo Nov 19 23:17:33 alchemy kernel: [27901.371065] usb 1-2: new high speed USB device using ehci_hcd and address 3 Nov 19 23:17:33 alchemy kernel: [27901.487101] usb 1-2: New USB device found, idVendor=152d, idProduct=2338 Nov 19 23:17:33 alchemy kernel: [27901.487137] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Nov 19 23:17:33 alchemy kernel: [27901.487155] usb 1-2: Product: USB to ATA/ATAPI Bridge Nov 19 23:17:33 alchemy kernel: [27901.487170] usb 1-2: Manufacturer: JMicron Nov 19 23:17:33 alchemy kernel: [27901.487182] usb 1-2: SerialNumber: 222256D1009C Nov 19 23:17:33 alchemy kernel: [27901.487522] usb 1-2: configuration #1 chosen from 1 choice Nov 19 23:17:33 alchemy kernel: [27901.489407] scsi6 : SCSI emulation for USB Mass Storage devices Nov 19 23:17:33 alchemy kernel: [27901.489802] usb-storage: device found at 3 Nov 19 23:17:33 alchemy kernel: [27901.489808] usb-storage: waiting for device to settle before scanning Nov 19 23:17:34 alchemy kernel: [27902.490176] scsi 6:0:0:0: Direct-Access ST932032 5AS SDM1 PQ: 0 ANSI: 2 CCS Nov 19 23:17:34 alchemy kernel: [27902.491175] sd 6:0:0:0: Attached scsi generic sg2 type 0 Nov 19 23:17:34 alchemy kernel: [27902.492454] usb-storage: device scan complete Nov 19 23:17:34 alchemy kernel: [27902.522537] sd 6:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) Nov 19 23:17:34 alchemy kernel: [27902.523751] sd 6:0:0:0: [sdb] Write Protect is off Nov 19 23:17:34 alchemy kernel: [27902.523782] sd 6:0:0:0: [sdb] Mode Sense: 00 38 00 00 Nov 19 23:17:34 alchemy kernel: [27902.523790] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:34 alchemy kernel: [27902.526271] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:35 alchemy kernel: [27902.526323] sdb: sdb1 sdb2 sdb3 sdb4 Nov 19 23:17:35 alchemy kernel: [27902.896183] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:35 alchemy kernel: [27902.896222] sd 6:0:0:0: [sdb] Attached SCSI disk Nov 19 23:18:06 alchemy kernel: [27933.803081] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:18:36 alchemy kernel: [27964.020066] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:13 alchemy kernel: [28000.803086] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:28 alchemy kernel: [28015.905071] usb 1-2: device descriptor read/64, error -110 Nov 19 23:19:43 alchemy kernel: [28031.108069] usb 1-2: device descriptor read/64, error -110 Nov 19 23:19:43 alchemy kernel: [28031.311072] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:58 alchemy kernel: [28046.413082] usb 1-2: device descriptor read/64, error -110 Nov 19 23:20:14 alchemy kernel: [28061.616069] usb 1-2: device descriptor read/64, error -110 Nov 19 23:20:14 alchemy kernel: [28061.819069] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:20:14 alchemy kernel: [28062.243051] usb 1-2: device not accepting address 3, error -71 Nov 19 23:20:14 alchemy kernel: [28062.345314] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:20:25 alchemy kernel: [28072.747067] usb 1-2: device not accepting address 3, error -110 Nov 19 23:20:25 alchemy kernel: [28072.747183] sd 6:0:0:0: Device offlined - not ready after error recovery Nov 19 23:20:25 alchemy kernel: [28072.747237] sd 6:0:0:0: [sdb] Unhandled error code Nov 19 23:20:25 alchemy kernel: [28072.747385] sd 6:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Nov 19 23:20:25 alchemy kernel: [28072.747409] end_request: I/O error, dev sdb, sector 53528580 Nov 19 23:20:25 alchemy kernel: [28072.747431] Buffer I/O error on device sdb4, logical block 0 Nov 19 23:20:25 alchemy kernel: [28072.747453] Buffer I/O error on device sdb4, logical block 1 Nov 19 23:20:25 alchemy kernel: [28072.747469] Buffer I/O error on device sdb4, logical block 2 Nov 19 23:20:25 alchemy kernel: [28072.747486] Buffer I/O error on device sdb4, logical block 3 Nov 19 23:20:25 alchemy kernel: [28072.747503] Buffer I/O error on device sdb4, logical block 4 Nov 19 23:20:25 alchemy kernel: [28072.747512] Buffer I/O error on device sdb4, logical block 5 Nov 19 23:20:25 alchemy kernel: [28072.747519] Buffer I/O error on device sdb4, logical block 6 Nov 19 23:20:25 alchemy kernel: [28072.747527] Buffer I/O error on device sdb4, logical block 7 Nov 19 23:20:25 alchemy kernel: [28072.747543] Buffer I/O error on device sdb4, logical block 8 Nov 19 23:20:25 alchemy kernel: [28072.747752] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.747842] sd 6:0:0:0: [sdb] Unhandled error code Nov 19 23:20:25 alchemy kernel: [28072.747858] sd 6:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Nov 19 23:20:25 alchemy kernel: [28072.747878] end_request: I/O error, dev sdb, sector 53528708 Nov 19 23:20:25 alchemy kernel: [28072.748103] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748169] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748260] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748293] usb 1-2: USB disconnect, address 3 Nov 19 23:20:25 alchemy kernel: [28072.748300] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.855055] usb 1-2: new high speed USB device using ehci_hcd and address 4 Nov 19 23:20:25 alchemy kernel: [28072.981040] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:30 alchemy kernel: [28078.206065] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:30 alchemy kernel: [28078.409069] usb 1-2: new high speed USB device using ehci_hcd and address 5 Nov 19 23:20:30 alchemy kernel: [28078.548243] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:41 alchemy kernel: [28088.761069] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:41 alchemy kernel: [28088.964070] usb 1-2: new high speed USB device using ehci_hcd and address 6 Nov 19 23:20:51 alchemy kernel: [28099.366060] usb 1-2: device not accepting address 6, error -110 Nov 19 23:20:51 alchemy kernel: [28099.417345] hub 1-0:1.0: unable to enumerate USB device on port 2 Nov 19 23:21:33 alchemy kernel: [28140.805088] usb 1-2: new high speed USB device using ehci_hcd and address 8 Nov 19 23:21:33 alchemy kernel: [28140.921050] usb 1-2: New USB device found, idVendor=152d, idProduct=2338 Nov 19 23:21:33 alchemy kernel: [28140.921089] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Nov 19 23:21:33 alchemy kernel: [28140.921107] usb 1-2: Product: USB to ATA/ATAPI Bridge Nov 19 23:21:33 alchemy kernel: [28140.921122] usb 1-2: Manufacturer: JMicron Nov 19 23:21:33 alchemy kernel: [28140.921134] usb 1-2: SerialNumber: 222256D1009C Nov 19 23:21:33 alchemy kernel: [28140.921640] usb 1-2: configuration #1 chosen from 1 choice Nov 19 23:21:33 alchemy kernel: [28140.923927] scsi7 : SCSI emulation for USB Mass Storage devices Nov 19 23:21:33 alchemy kernel: [28140.924873] usb-storage: device found at 8 Nov 19 23:21:33 alchemy kernel: [28140.924883] usb-storage: waiting for device to settle before scanning Nov 19 23:21:34 alchemy kernel: [28141.925259] scsi 7:0:0:0: Direct-Access ST932032 5AS SDM1 PQ: 0 ANSI: 2 CCS Nov 19 23:21:34 alchemy kernel: [28141.931805] sd 7:0:0:0: Attached scsi generic sg2 type 0 Nov 19 23:21:34 alchemy kernel: [28141.934500] usb-storage: device scan complete Nov 19 23:21:34 alchemy kernel: [28141.951408] sd 7:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) Nov 19 23:21:34 alchemy kernel: [28141.964372] sd 7:0:0:0: [sdb] Write Protect is off Nov 19 23:21:34 alchemy kernel: [28141.964394] sd 7:0:0:0: [sdb] Mode Sense: 00 38 00 00 Nov 19 23:21:34 alchemy kernel: [28141.964405] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28141.966441] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28141.966489] sdb: sdb1 sdb2 sdb3 sdb4 Nov 19 23:21:34 alchemy kernel: [28142.329129] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28142.329169] sd 7:0:0:0: [sdb] Attached SCSI disk Nov 19 23:21:35 alchemy kernel: [28143.104874] kjournald starting. Commit interval 15 seconds Nov 19 23:21:35 alchemy kernel: [28143.160204] kjournald starting. Commit interval 15 seconds Nov 19 23:21:35 alchemy kernel: [28143.160592] EXT3 FS on sdb3, internal journal Nov 19 23:21:35 alchemy kernel: [28143.160606] EXT3-fs: mounted filesystem with ordered data mode. Nov 19 23:21:35 alchemy kernel: [28143.162994] EXT3 FS on sdb4, internal journal Nov 19 23:21:35 alchemy kernel: [28143.163017] EXT3-fs: mounted filesystem with ordered data mode. Nov 19 23:31:30 alchemy kernel: [28737.803090] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:00 alchemy kernel: [28768.020047] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:37 alchemy kernel: [28804.803097] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:47 alchemy kernel: [28814.915062] usb 1-2: device descriptor read/64, error -71 Nov 19 23:32:47 alchemy kernel: [28815.153078] usb 1-2: device descriptor read/64, error -71 Nov 19 23:32:47 alchemy kernel: [28815.356065] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:02 alchemy kernel: [28830.458065] usb 1-2: device descriptor read/64, error -110 Nov 19 23:33:18 alchemy kernel: [28845.661074] usb 1-2: device descriptor read/64, error -110 Nov 19 23:33:18 alchemy kernel: [28845.864062] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:23 alchemy kernel: [28851.278070] usb 1-2: device not accepting address 8, error -110 Nov 19 23:33:23 alchemy kernel: [28851.380096] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:24 alchemy kernel: [28851.803056] usb 1-2: device not accepting address 8, error -71 Nov 19 23:33:24 alchemy kernel: [28851.803183] sd 7:0:0:0: Device offlined - not ready after error recovery Nov 19 23:33:24 alchemy kernel: [28851.803220] sd 7:0:0:0: [sdb] Unhandled error code Nov 19 23:33:24 alchemy kernel: [28851.803234] sd 7:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Nov 19 23:33:24 alchemy kernel: [28851.803277] end_request: I/O error, dev sdb, sector 199411716 Nov 19 23:33:24 alchemy kernel: [28851.803405] sd 7:0:0:0: rejecting I/O to offline device Nov 19 23:33:24 alchemy kernel: [28851.803460] usb 1-2: USB disconnect, address 8 Nov 19 23:33:24 alchemy kernel: [28851.812524] Aborting journal on device sdb4. Nov 19 23:33:24 alchemy kernel: [28851.812659] journal commit I/O error Nov 19 23:33:24 alchemy kernel: [28851.881415] ------------[ cut here ]------------ Nov 19 23:33:24 alchemy kernel: [28851.881466] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.31.5/linux-2.6.31/fs/buffer.c:1158 mark_buffer_dirty+0xa6/0xd0() <snip> So far this seems to effect the x86_64 box and not the i586 box. I have the same drive attached to the i586 box right now and the logs are clean and the drive is working fine.. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 9