Hi Mr Cristopher .M. Penalver I did update yesterday ,my BIOS (1.90) as you have told me to do , but i faced later at night problems again with the screen (was getting darker and i was not able to do anything on my computer even alt+f2 was not stable on the screen ,was coming out and disappearing right away before do anything on it,and when ,after a lot of pressing alt+f2 came out and stable ,during the collecting informations got even this window dark and stop collecting any information) I had to turn off the electricity. Today in the morning the computer was not connected to ubuntu and i had to turn off the electricity twice and start it again until i got connected. So i decided to open the terminal as you have told me and put the command "sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date" as you had told me to do in case that i face again after the BIOS (1.90) updated. I did so and i was ask in the terminal to put my ubuntu password !! I did PUT it ,i press enter after but i do not have anything in my home folder to attach on this ANSWER which i send you right now ,as it had happenned with the other command i had put in the terminal ,"lsusb -v > lsusb-v.log" , i think 2 days ago. Is it ok that i gave my password to the terminal?? Is it normal that i have nothing in my home folder after that , so i can attach it to you ,as i did last time?? What is really happens in my laptop by these people?? What are proposing me to do?? Please i need your help even i know that i do have overtired you about my case. I WAS LOOKING ONE MORE TIME TO SEE IF ANYTHING HAS BEEN IN MY FOLDERS OUT OF THIS TERMINAL COMMAND AND I FOUND IN MY DOWNLOADS THE /home/ubuntu/Downloads/FTS_FLASHBIOSUPDATEMSIMS6178MVER19032301_19_23206.EXE but i cannot attach it says this kind of file so i got a screen photo of it and i attach it to you!!! THANK YOU one more time Babis Xanthopoulos -------------------------------------------------------------------------------------------------------------------------------------
> Date: Mon, 15 Jul 2013 11:03:06 +0000 > From: christopher.m.penal...@gmail.com > To: babisxanthopou...@hotmail.com > Subject: [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to > crash Xorg > > babis x, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an > update is available for your BIOS (1.90). If you update to this, does it > change anything? > > If not, could you please both specify what happened, and provide the output > of the following terminal command: > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date > > Thank you for your understanding. > > ** Summary changed: > > - A wrong hardware detection seems to crash Xorg > + 045e:0745 A wrong hardware detection seems to crash Xorg > > ** Tags added: bios-outdated-v1.9 needs-upstream-testing regression- > potential > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1191334 > > Title: > 045e:0745 A wrong hardware detection seems to crash Xorg > > Status in "linux" package in Ubuntu: > Incomplete > Status in "xserver-xorg-input-synaptics" package in Ubuntu: > Incomplete > > Bug description: > A wrong hardware detection seems to crash Xorg. This report is > generated without a wireless mouse, which was connected to the laptop > in the duplicate bug 1190987 but the mouse didn't make a difference to > the system's stability. Both the xorg.log and the attachment refer to > a "Microsoft MicrosoftR Nano Transceiver" but the laptop is not > connected a a wireless keyboard. > > > From Xorg.log: > > (EE) Backtrace: > (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] > (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] > (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] > (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] > (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) > [0xb6ee9bad] > (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) > [0xb6eeb286] > (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] > (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] > (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] > (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] > (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] > (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] > (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] > (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] > (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] > (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] > (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] > (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] > (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] > (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] > (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] > (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] > (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] > (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] > (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] > (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] > (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] > (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] > (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] > (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] > (EE) > (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher > up the stack. > (EE) [mi] mieq is *NOT* the cause. It is a victim. > [mi] Increasing EQ size to 512 to prevent dropped events. > [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. > [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing > the server's resources. > [ 20581.964] (II) config/udev: removing device Microsoft MicrosoftR Nano > Transceiver v2.0 > [ 20586.862] (II) evdev: Microsoft MicrosoftR Nano Transceiver v2.0: Close > [ 20588.924] (II) UnloadModule: "evdev" > > ProblemType: Bug > DistroRelease: Ubuntu 13.04 > Package: xorg 1:7.7+1ubuntu4 > ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 > Uname: Linux 3.8.0-25-generic i686 > .tmp.unity.support.test.0: > > ApportVersion: 2.9.2-0ubuntu8.1 > Architecture: i386 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > Date: Sat Jun 15 18:34:14 2013 > DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job > DistroCodename: raring > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GpuHangFrequency: Several times a day > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Since before I upgraded > GraphicsCard: > Advanced Micro Devices [AMD] nee ATI RC410M [Mobility Radeon Xpress 200M] > [1002:5a62] (prog-if 00 [VGA controller]) > Subsystem: Fujitsu Technology Solutions Device [1734:10fb] > InstallationDate: Installed on 2013-02-12 (123 days ago) > InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 > (20121017.2) > Lsusb: > Bus 003 Device 003: ID 046d:0a10 Logitech, Inc. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > MachineType: FUJITSU SIEMENS AMILO Li 1718 > MarkForUpload: True > ProcEnviron: > PATH=(custom, no user) > XDG_RUNTIME_DIR=<set> > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic > root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to raring on 2013-05-14 (31 days ago) > dmi.bios.date: 06/25/07 > dmi.bios.vendor: Phoenix > dmi.bios.version: V1.8 > dmi.board.name: AMILO Li 1718 > dmi.board.vendor: FUJITSU SIEMENS > dmi.board.version: Rev.A > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 1 > dmi.chassis.vendor: ATI > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: > dmi.product.name: AMILO Li 1718 > dmi.product.version: -1 > dmi.sys.vendor: FUJITSU SIEMENS > version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 > version.libdrm2: libdrm2 2.4.43-0ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 > version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.7.3-0ubuntu2b2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 > version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.7-0ubuntu1 > xserver.bootTime: Sat Jun 15 11:25:40 2013 > xserver.configfile: default > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.13.3-0ubuntu6 > xserver.video_driver: radeon > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191334/+subscriptions ** Attachment added: "Screenshot from 2013-07-16 140616.png" https://bugs.launchpad.net/bugs/1191334/+attachment/3738685/+files/Screenshot%20from%202013-07-16%20140616.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1191334 Title: 045e:0745 A wrong hardware detection seems to crash Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191334/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
