September 2008 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] Mouse stuttering on Dell Precision M4300
by Dominique Leuenberger 01 Sep '08

01 Sep '08

On Fri, 2008-08-29 at 16:44 -0700, John Andersen wrote: > On Fri, Aug 29, 2008 at 1:35 AM, Dominique Leuenberger > <Dominique.Leuenberger(a)tmf-group.com> wrote: > > Hi, > > > > I have several Dell Precision M4300 Notebooks, they all suffer from the > > same problem: > > > > Once in a while (to frequent... normally after a short break, while > > reading something), the mouse stutters and only works again after about > > 30 seconds. Mostly it happens if the mouse was not used for a while. > > > > It is quiet annoying as you can imagine ;) > > > > My normal configuration is openSUSE 11.0, with the proprietary nVidia > > driver, compiz activated. > > > > In process of elimination, I disabled compiz, mouse continues > > stuttering. > > Next step was to use the nv driver instead of nvidia, mouse stutterig > > still happens. > > > > Does anybody know of a trick that's missing here? > > > > Thanks for all your suggestions, > > Dominique > > Mouse has almost nothing to do with your video drivers. > > How about telling us about the mouse? > USB? Wireless? Bluetooth? > > A usb mouse on the same USB controller as a network card > can run out of bandwidth. > > A wireless mouse might be going into battery save mode. > (when did you last change batteries?) Correct, ALMOST nothing ;)... but there are options swmouse or hwmouse (which, in fact did not change). The problem happens with the internal touchpad, the internal pointer and with an externam usb mouse. Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Problems with USB GPS-device
by Rikard Johnels 01 Sep '08

01 Sep '08

Hello all! I have a strange problem with a USB GPS device that wont "sync" its datastream with the device node.. (Or how i would describe it) Kernel bversion: 2.6.16.21-0.8-smp gpsd version: 2.37 SuSE version: SUSE Linux Enterprise Desktop 10 (i586) I am was using gpsd version 2.09 on SLED 10 sp1, and a BU-353 USB GPS Receiver. I ran gpsdrive over that and it worked nicely. I tried updating to 2.10pre4 via repository. But i run into some problems. I cant seem to get my USB GPS reciever to work after that. I can see in /var/log/messages that it is found and gives it the ttyUSB0 device. I can see the gpsd starting up as /usr/sbin/gpsd -F /var/run/gpsd.socket /dev/ttyUSB0 but i cant telnet to 2947, it doesnt give anything at all.. No echo no nothing. I tried hexdump -C /dev/ttyUSB0, but it mostly gives me gabled output. It is as if the reading of the datastream doesnt sync. It starts of with thousands of 0x00 and 0x80 then going into random data, and once in a short while slip into readable data. It doesnt stay that way for more than a few seconds if at all... Here are a few snippets from hexdump: 00000000 80 00 78 00 80 78 80 78 f8 80 80 78 80 f8 80 00 |..x..x.x...x....| 00000010 80 78 f8 80 78 80 00 78 78 00 f8 00 78 78 80 00 |.x..x..xx...xx..| 00000020 78 00 80 00 80 00 78 78 80 80 78 78 80 00 78 80 |x.....xx..xx..x.| Initial start 00000110 00 80 00 78 78 f8 00 78 78 f8 80 78 80 78 80 f8 |...xx..xx..x.x..| 00000120 f8 80 80 78 78 f8 80 78 80 00 80 00 80 00 78 80 |...xx..x......x.| 00000130 80 f8 00 78 00 80 78 80 00 80 78 80 78 f8 80 80 |...x..x...x.x...| A while later 00005670 00 78 78 80 f8 00 78 00 78 00 80 00 80 00 80 00 |.xx...x.x.......| 00005680 80 80 78 80 80 f8 80 00 80 78 00 80 78 00 80 80 |..x......x..x...| 00005690 f8 00 70 3b 25 a5 59 55 a2 2b f5 96 55 b4 96 56 |..p;%.YU.+..U..V| 000056a0 d4 56 56 56 55 56 55 54 54 14 35 a7 a2 e4 27 51 |.VVVUVUTT.5...'Q| 000056b0 95 d4 94 97 94 36 25 d9 55 a2 d9 95 b3 51 d1 95 |.....6%.U....Q..| 000056c0 05 dd 29 70 37 a5 d1 b5 59 a2 a2 94 56 25 95 a5 |..)p7...Y...V%..| 000056d0 76 55 a2 95 b3 b7 25 51 dd 09 74 b9 25 59 55 2b |vU....%Q..t.%YU+| Then readable text: 000066f0 b6 56 f7 71 53 91 b7 7a aa aa a2 65 b4 f6 54 95 |.V.qS..z...e..T.| 00006700 54 b4 96 54 b5 96 96 2c 32 31 2c 31 36 2c 31 34 |T..T...,21,16,14| 00006710 2c 24 47 50 47 53 56 2c 33 2c 33 2c 31 32 2c 30 |,$GPGSV,3,3,12,0| 00006720 38 2c 31 34 2c 33 32 37 2c 32 35 2c 32 36 2c 31 |8,14,327,25,26,1| 00006730 34 2c 30 31 38 2c 2c 32 37 2c 30 38 2c 33 30 32 |4,018,,27,08,302| 00006740 2c 33 36 2c 30 37 2c 30 37 2c 32 39 31 2c 33 30 |,36,07,07,291,30| 00006750 2a 37 45 0d 0a 24 47 50 52 4d 43 2c 32 30 2c 35 |*7E..$GPRMC,20,5| 00006760 39 31 37 2e 35 39 30 35 2c 4e 2c 30 31 38 31 35 |917.5905,N,01815| Back to nonsense: 00009820 2c 31 0d 0a 50 52 4d 32 30 30 30 2c 35 39 31 4e |,1..PRM2000,591N| 00009830 2c 30 31 35 33 37 2c 30 2e 2c 32 2e 2c 32 30 38 |,01537,0.,2.,208| 00009840 2c 2c 30 31 0d 0a 47 41 2c 32 30 35 38 30 30 30 |,,01..GA,2058000| 00009850 2c 37 2e 31 31 2c 30 31 2e 36 37 2c 45 2c 30 2e |,7.11,01.67,E,0.| 00009860 39 30 2e 38 2c 32 2c 4d 2c 30 30 2a 36 0a 24 47 |90.8,2,M,00*6.$G| 00009870 2c 41 2c 2c 31 32 37 2c 2c 30 2c 30 31 35 2c 32 |,A,,127,,0,015,2| 00009880 2c 35 2c 2e 39 0d 0a 24 47 43 2c 34 2e 30 2c 41 |,5,.9..$GC,4.0,A| 00009890 39 31 31 2c 31 38 2e 36 31 2c 45 31 36 2c 34 32 |911,18.61,E16,42| 000098a0 2c 30 38 30 2c 0a 47 47 18 78 78 e6 78 00 78 86 |,080,.GG.xx.x.x.| 000098b0 66 78 1e f8 86 66 78 f8 78 e0 78 00 78 e0 78 78 |fx...fx.x.x.x.xx| 000098c0 e0 78 e6 78 86 06 78 86 00 86 00 78 86 86 78 78 |.x.x..x....x..xx| 000098d0 86 7e 78 86 e6 98 f8 86 86 78 86 00 78 78 78 1e |.~x......x..xxx.| 000098e0 e6 80 60 00 e6 7e 9e 86 06 1e 86 1e 78 1e e0 86 |..`..~......x...| 000098f0 06 78 e0 1e e6 60 66 9e 60 06 1e 86 78 e6 78 00 |.x...`f.`...x.x.| 00009900 78 86 66 78 78 1e f8 f8 78 e0 78 f8 98 e0 86 00 |x.fxx...x.x.....| 00009910 78 78 86 78 78 e0 78 78 78 78 78 86 00 78 78 86 |xx.xx.xxxxx..xx.| 00009920 06 78 86 18 78 86 e6 18 78 78 78 86 e6 98 e0 86 |.x..x...xxx.....| 00009930 78 78 78 60 e6 80 e6 7e 9e 98 9e 00 1e 86 1e 78 |xxx`...~.......x| 00009940 f8 78 1e e0 86 00 78 1e e0 86 06 1e e6 60 e0 86 |.x....x......`..| 00009950 7e 78 1e f8 e0 78 86 00 78 78 78 86 1e 78 98 80 |~x...x..xxx..x..| The device is working flawlessly under Windows XP on the same machine. No problems whatsoever. very fast to lock to satelites. Where shall i go on looking for problems? Kernel problems with the USB device driver reading the stream?? /Rikard

3 3

Re: [opensuse] Printer Recommendation?
by Fred A. Miller 01 Sep '08

01 Sep '08

Lew Wolfgang wrote: > Yup, maybe HP is the answer. I've also had good > luck with more recent Xerox Phaser laser printers, > but that's a bit more than I want to pay for an > infrequently used home system. > > Thanks for your help! > Lew Happy to. > (btw, I was using an HP Laserjet 4000 up until two > weeks ago, but I had to return it to my employer since > I'm retiring next week. I'm planning on returning to > work as a contractor within a few weeks, but I still > need my own system now.) [snip] Ok.....the HP I have does up through 13x19" awesome photos and works very well with Linux. I plan to semi-retire next year, but that depends on the elections this Fall. If NOBama is elected, I won't be able to.....have to wait and see. Enjoy your retirement! Fred -- Linux is an old Latin word meaning, "I don't have to support your Windows anymore." -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] How to allocate more space to windows...
by Mukul Singh 01 Sep '08

01 Sep '08

Hi all, I have a laptop which came with Windows Vista. I installed OpenSuse 10.3 on it. The total hard disk was 160 GB out of which opensuse is using around 100 GB. Is it possible to allocate more space to Vista? Regards -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Multiple <gdm[2526]: DEBUG: ...> Startup Error Messages
by Jay Mistry 01 Sep '08

01 Sep '08

I get muliple <gdm[2526]: DEBUG: ...> Error Messages in openSUSE 11.0, updated to date. This is an x86 version. I have set the boot type to 'verbose' in grub settings (in Yast). After selecting the default openSUSE 11.0 from grub menu, these [debug....] Error Messages scroll down at the same speed (i.e. the boot process does not halt anywhere in between) and ultimately the PC boots up to the Login Screen. The complete bootup log from /var/log/boot.msg is here (Nopaste url): http://rafb.net/p/fUw4Xu28.html Any hints/suggestions towards troubleshooting? Thanks, -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 6

Re: [opensuse] Opensuse doesn't wait long enough for the disks to spin up before trrying to configure raid
by Mike Myers 01 Sep '08

01 Sep '08

I agree with you that it doesn't seem to make sense to have the delay time between spinup initiation and assembly stage to be fixed irrespective of disks. Hopefully adjust the timeout will fix it, but something does seem wrong with the way this is currently architected. I am very sure there are no BIOS options to spin up the disks, either staggered or all at once. I have an adaptec 1430SA, plus two SI3132 based serial ATA controllers. The BIOS of all the cards has no such option, though the motherboard ports I do believe obey the motherboard BIOS disk delay parameter. And I know the Adaptec controller and the SI 3132 BIOS does not support port multipliers - they only "see" the disk on port 0 of the PMP, not the other 4. So since it only sees one disk, I do not believe that it is possible for it to spin the other guys up. The only code that understands PMP's are there is libata, so if staggered spinup or group spinup (2 or 3 at a time) is to be implemented, it would have to be done in the libata code. The only thing that happens now is spinup during the hotplug sequence, and even thenj it's not explicitly sttable - I couldn't do simultaneous spinup even if I wanted too. It would be good if the software raid configuration that libata does would have these same capabilities for controlling spinup and other items that hardware raid controllers do. After all, software raid should be able to be much more flexible and configurable than a hardware raid controller. If I'm offtrack here, I'd love to be proven wrong, but I've built software raid basd NAS's for 3 years now, and have always seen the process work as I've described it. thx mike ----- Original Message ---- From: Brian K. White <brian(a)aljex.com> To: opensuse(a)opensuse.org Sent: Sunday, August 31, 2008 7:35:58 PM Subject: Re: [opensuse] Opensuse doesn't wait long enough for the disks to spin up before trrying to configure raid ----- Original Message ----- From: "Mike Myers" <mikesm559(a)yahoo.com> To: <opensuse(a)opensuse.org> Sent: Saturday, August 30, 2008 3:31 PM Subject: Re: [opensuse] Opensuse doesn't wait long enough for the disks to spin up before trrying to configure raid >I don't think that's going to fix it. The way the libata > driver works is that it spins the disks up one at a time > (staggered spinup). Just powering the system on will not > cause the disks to spin up. After the start of the boot, > / is mounted and the sata driver begins doing all of it's > work, finding the PMP's on the SATA ports, and then probing > each PMP, id'ing the disks and spinning them up, etc... > So this is all happening way after the boot is started. Every piece of hardware I ever saw spun the disks up on it's own, and that includes lots of scsi and sata and sas raid arrays, including the use of sata port expanders/multiplexers. Usually the bios involved (maybe a raid card, maybe a motherboard) offers an option to stagger the spinup, configureable seconds between disks, or configurable seconds between sets of N(configurable) disks at once, configurable seconds to wait in total, or all of the above. Then libata will find every disk ready to go on the first try and that whole sequence should shoot through fast and not screw up md mounting. However I do think the way you are trying to fix it is the more correct fix. The assmbly and mount stages should obviously block until the spinup stage is done, and the spinup stage should obviously have a timeout per disk and no fixed total timeout. However-However... Even IF the raid card and mb offer no way to avoid starting all disks at once, a box like that should probably have a dual or triple redundant, hot-swap power supply anyways. (you bought 18 hot swap disks but only a plain jane single not-hot-swap ps?) It might be too much for one power supply to spin up all at once, but as long as you have both plugged in and both work, then no problem. You're only vulnerable when one ps dies until you get it's replacement in. And since they're hot swap, you can have the spare sitting there on hand already and pop it in immediately. -- Brian K. White brian(a)aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

Re: [opensuse] Opensuse doesn't wait long enough for the disks to spin up before trrying to configure raid
by Mike Myers 01 Sep '08

01 Sep '08

I don't think that's going to fix it. The way the libata driver works is that it spins the disks up one at a time (staggered spinup). Just powering the system on will not cause the disks to spin up. After the start of the boot, / is mounted and the sata driver begins doing all of it's work, finding the PMP's on the SATA ports, and then probing each PMP, id'ing the disks and spinning them up, etc... So this is all happening way after the boot is started. thx mike ----- Original Message ---- From: Ken Schneider <suse-list3(a)bout-tyme.net> To: opensuse(a)opensuse.org Sent: Saturday, August 30, 2008 12:26:16 PM Subject: Re: [opensuse] Opensuse doesn't wait long enough for the disks to spin up before trrying to configure raid Mike Myers pecked at the keyboard and wrote: > Hi. I have a Opensuse 11.0 system running as a server with about 18 data disks hooked to the local motherboard SATA ports, and 3 SATA port multipliers hooked to a Adaptec 1430SA controller. Because of how the PMP code works and how long it takes to spin up each disk, it can take awhile before the disks are all spun up and online. About half the time I boot the system, OpenSUSE thinks the disks are already up and proceeds to run the /etc/init.d/boot.md and boot.lvm files, which of course fail to assemble the disks because they haven't fully come online yet, and dumps me into a single-user mode shell to fix the disks. > > The bottom line is about half the time I try to boot the system, it fails and needs some console work before I can bring it up. Does anyone know if there is a fixed time delay somewhere that waits for the disks to spin up or does it use a different way of telling if it's done? > > Thanks, > Mike > There is a time delay at the boot screen that can be used to delay the boot process. timeout 8 Gives an 8 second delay, no reason you can't make it 30 to allow all of the disks to spin up. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] Window decorations in openSUSE 11.0 Compiz/KDE3.5.9
by Jay C Vollmer 01 Sep '08

01 Sep '08

Greetings. I've just installed openSUSE 11.0 from the KDE4 Live CD on my ThinkPad T61p. I'm delighted to see that suspend to RAM now works as well as the ipw3945, neither of which worked right in 10.3. What isn't working for me in openSUSE 11.0 is the window-decoration when I use Compiz with KDE3. The title-bars of non-active windows completely disappear. Can anyone suggest a solution so my inactive titlebars don't disappear? -- JAY VOLLMER TEXT REFS DOUBLEPLUSSUNGOOD SELFTHINK VERGING CRIMETHINK IGNORE FULLWISE -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2