[Bug 1082418] Re: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode
Dear All, especiall UBUNTU Ubiquity team and The Boss (Mr. Mark) It has been long time since I report this bug. And so many of us are effected. Today I have made experiments and have short cl1&cl2 many times again to help UBUNTU community. I have reformat my SSD and install Windows 10 in UEFI mode, BIOS F12 is preserved 100% perfect. Then I install 18.04 AND REDONE CL1&CL2 THEN 16.04 UBUNTU AND Lubuntu 18.04. ALL experimentS UBUNTU all versions destroyed LH532 Bios F12 functions and need to short CL1&CL2 to bring BIOS F12. BIOS F2 is still dead. I have AGAIN reformat my SSD and install Windows 10 in UEFI mode, BIOS F12 is preserved 100% perfect. I INSTALLED Manjaro LINUX in the second half of the non format hard disk. It resulted in very excellent installation, BIOS F12 is preserved 100% perfect. THEN I proceed to install UBUNTU 18.04, it is very smart in auto mode, request me to approve 50% re partitioning only for Manjaro Linux and not Windows 10. So I did approved that. Resulted in : 1. Windows 10 boot ok. 2. UBUNTU 18.04 jealously destroyed access to Manjaro Linux, did Mr Mark order this 3. It destroyed BIOS F12 and I have to short CL1&CL2 to get my BIOS F12. SO I would like to confirm here UBUNTU 18.04 UBIQUITY HAS NOT BEEN IMPROVED. It is worse than 16.04 in detecting existing BIOS LEGACY MODE installation. And it is still maintain the bugs in destroying host computer BIOS. BUT MANJARO installation program and Windows 10 works fine. Something wrong in UBUNTU INSTALLATION PROCESS since 12.04. and no one care to change that. I hope this existing bugs will destroy MR MARK's NEW NOTEBOOK in the future. I really hope that. So he will order the fixing of these bugs. Best Regards to Everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771675] [NEW] Ubuntu18.04 fail to install grub and destroy existing grub
Public bug reported: It is similar almost the same. But I decide to file a separate report of bugs from https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703 Because it destroy existing grub that was not reported there. And this time I hope the guru will see what informations were correct from my machine. Lubuntu 18.04, Ubuntu 18.04 destroy my existing ubuntu 16.04 installed grub. I did explain how I make my computer boot again in askubuntu link https://askubuntu.com/questions/1028921/the-grub-efi-amd64-signed- package-failed-to-install-into-target-during-ins/1030317#1030317 Best Regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Thu May 17 06:23:59 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771675 Title: Ubuntu18.04 fail to install grub and destroy existing grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
Sorry I could not find the old edit link to go and edit my post so I repeat the part that need modifications/ My conclusion is Moderator must now file this as real bugs in 18.04 The bugs lies in the 4 parts. 1. It did not detect that we have BIOS mode installations in place, like the 16.04.4 and older version (I have not tried 17. at all). So It keep going to install to efi partition which resulted in this error. 2. I belived I did find once or twice in some different configuration that it present the choice at the beginning of the installation process and I chose Bios. But still got the same result of same errors. But some how most of time no questions ask at the begging. 3. It should have check if the efi partition exist before it activate the efi installation mode. I did not have EFI partition on purpose, And It should find that easily by use the program algorithm. 4. At the end error last 2 warning page freezed and stay there until we reboot. except Lubuntu 18.04 allow us to close the error warning pages. So even within 18.04 there are bugs for sure. Lubuntu did not have this 4th bug while the UBUNTU AND KYLIN HAS. I hope the Guru will have some clues by now how to find these bugs and fix it. Best Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
@Graham Mitchell (graham-grahammitchell) I view the same as yours. More though, there is or are the bugs somewhere in the new 18.04 Ubuntu, Kylyn, Lubuntu. I confirmed the problems. https://askubuntu.com/questions/1028921/the-grub-efi-amd64-signed- package-failed-to-install-into-target-during-ins/1037036#1037036 My conclusions they are another very bad bugs. Since the all old 16.04 works fine for exact same environments. All 16.04 will detect my notebook is uefi, and will have the installation screen as uefi mode. But since I purposely do not provide efi partition. In order to force all installation to prohibit UEFI mode which I did make mistake again with new SSD half a year back on 16.04.4 fresh installation. End up no F12. And I have to open up my broken notebook to short jumpers again to get F12 BACK. So the installation process will warn me in all 16.04 flavors, UBUNTU Mint Mate lubuntu kylyn xubuntu. And I will choose to click on go back button to FORCE BIOS mode installation. But I did not encounter the same warning from any of my 6-7 times on my LH532 notebook with 18.04 Ubuntu Kylyn nor Lubuntu. Therefore, I have no chance to force the installation process back to activate BIOS installation mode. My conclusion the bugs lies in the 3 parts. 1. It did not detect that we have BIOS mode installations in place like the 16.04.4 and older version (I have not tried 17. at all) so I will keep on going to find efi partition to install uefi ubuntu. 2. It should have check if the efi partition exist before it activate the efi installation mode. 3. At the end error last 2 warning page freez and stay there until we reboot. except Lubuntu 18.04 allow us to close the freez warning page. I hope the Guru will have some clues by now how to find these bugs and fix it. Best Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1082418] Re: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode
Dear Fillippo Do you mean.1. After we inatalled uefi ubuntu and it destroy Lifebook multi boot function in Bios.2. Instead of opening the Main Board to shorting CL1/CL2 posts, you can retorethe Option of Multiboot of the bios by just adding an entry via windows using an uefi entry manager? If yes please give us more details. How to do that please. I will try on my notebook. Sent from Yahoo7 Mail on Android On Tue, 17 Apr. 2018 at 2:55 am, Filippo Falezza<1082...@bugs.launchpad.net> wrote: Solved, I added an entry via windows using an uefi entry manager ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode Status in linux package in Ubuntu: Fix Released Bug description: lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.00-7ubuntu11 Candidate: 2.00-7ubuntu11 Pheonix Secure Core Tiano bios version 1.09 New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled. All functions worked normally when running Win7. Ubuntu 12.10 installed using whole disk. Installation successful Ubuntu boots and runs normally, however all access to the bios has now been lost. Pressing the default key (f2) during boot up is acknowledged by bios beep, but ignored and Ubuntu continues booting. In addition the 'boot choices' menu (f12) contains nothing but Ubuntu making it impossible to boot from USB or CD/DVD. The latter (f12) problem was overcome by opening up the machine, removing the ram and shorting the cl1/cl2 posts with a screwdriver. This restores the ability to boot from USB/CD by pressing f12 but does not restore bios access. The following recovery actions have been tried. 1) Install Boot-Repair, run repair, no change occurred. Boot repair report here: http://paste.ubuntu.com/1375041/ 2) Restore Windows from Clonezilla disk image (factory settings) - result - bios access is no longer possible from windows either, f2 now launches the Windows boot menu. 3) Update all drivers using Fujitsu driver update tool from within windows (which included a bios update). Result - no change, no bios. 4) Restored Ubuntu from Clonezilla disk image - no change. 5) Added second distro to disk. Installed successfully (uefi mode as that is all I have) no change to bios access. So overall result I have lost all bios access even from a reinstalled Windows. I repeat that bios access was perfectly normal before installing Ubuntu. I strongly suggest you read the contents of this thread in addition to the information here: http://ubuntuforums.org/showthread.php?t=2086602 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: grub-efi 2.00-7ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 23 15:50:07 2012 InstallationDate: Installed on 2012-11-22 (1 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Thanks Abdul, Hope you find another way to work around or solve the problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
As far as I know from Fujitsu staffs in Thailand, Fujitsu is no longer support UBUNTU on the note books. And they have erase all the files involved and said they cannot support the out side warranty products. Your notebook model has problems too. May be if it will lock out, like others? WARNING But some one find a way to fix it but not that easy. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418 http://ubuntuforums.org/showthread.php?t=2086602&page=3&p=12371918#post12371918 Your AH532 is different version of the notebook. It has bios for download. So it has better chance to re flash bios http://support.ts.fujitsu.com/productselect.asp?ParentsNavIDs=109754^109756&IDNR=&lng=EN http://support.ts.fujitsu.com/Download/Index.asp My LH532 serial no. has no bios download so I got stuck with no F2 Bios setup only F2 to boot menu still. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
I create 15.04 release desktop (not daily built) and copy linux-image-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb linux-headers-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb and execute the following command according to https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds ubuntu@ubuntu:~$ sudo dpkg -i *.deb Selecting previously unselected package linux-headers-4.1.0-040100rc3-generic. (Reading database ... 177841 files and directories currently installed.) Preparing to unpack linux-headers-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb ... Unpacking linux-headers-4.1.0-040100rc3-generic (4.1.0-040100rc3.201505102036) ... Selecting previously unselected package linux-image-4.1.0-040100rc3-generic. Preparing to unpack linux-image-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb ... Done. Unpacking linux-image-4.1.0-040100rc3-generic (4.1.0-040100rc3.201505102036) ... dpkg: dependency problems prevent configuration of linux-headers-4.1.0-040100rc3-generic: linux-headers-4.1.0-040100rc3-generic depends on linux-headers-4.1.0-040100rc3; however: Package linux-headers-4.1.0-040100rc3 is not installed. dpkg: error processing package linux-headers-4.1.0-040100rc3-generic (--install): dependency problems - leaving unconfigured Setting up linux-image-4.1.0-040100rc3-generic (4.1.0-040100rc3.201505102036) ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-3.19.0-15-generic The link /vmlinuz is a dangling linkto /boot/vmlinuz-3.19.0-15-generic Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic update-initramfs: Generating /boot/initrd.img-4.1.0-040100rc3-generic cryptsetup: WARNING: failed to detect canonical device of overlay cryptsetup: WARNING: could not determine root device from /etc/fstab ln: failed to create symbolic link ‘/root/lib/systemd/system/cdrom.mount’: No such file or directory run-parts: executing /etc/kernel/postinst.d/pm-utils 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic Errors were encountered while processing: linux-headers-4.1.0-040100rc3-generic ubuntu@ubuntu:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Christopher The above error using Ubuntu 15.04 dailybuild ISO from the link you gave in earlier post. I may do the wrong procedure or I have to choose earlier mainline kernel or what should I do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
ubuntu@ubuntu:~$ ls Desktop Documents Downloads Music Pictures Public Templates Videos ubuntu@ubuntu:~$ cd Downloads ubuntu@ubuntu:~/Downloads$ ls linux-headers-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb linux-image-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb ubuntu@ubuntu:~/Downloads$ sudo dpkg -i *.deb Selecting previously unselected package linux-headers-4.1.0-040100rc2-generic. (Reading database ... 177841 files and directories currently installed.) Preparing to unpack linux-headers-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb ... Unpacking linux-headers-4.1.0-040100rc2-generic (4.1.0-040100rc2.201505032335) ... Selecting previously unselected package linux-image-4.1.0-040100rc2-generic. Preparing to unpack linux-image-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb ... Done. Unpacking linux-image-4.1.0-040100rc2-generic (4.1.0-040100rc2.201505032335) ... dpkg: dependency problems prevent configuration of linux-headers-4.1.0-040100rc2-generic: linux-headers-4.1.0-040100rc2-generic depends on linux-headers-4.1.0-040100rc2; however: Package linux-headers-4.1.0-040100rc2 is not installed. dpkg: error processing package linux-headers-4.1.0-040100rc2-generic (--install): dependency problems - leaving unconfigured Setting up linux-image-4.1.0-040100rc2-generic (4.1.0-040100rc2.201505032335) ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-3.19.0-15-generic The link /vmlinuz is a dangling linkto /boot/vmlinuz-3.19.0-15-generic Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic update-initramfs: Generating /boot/initrd.img-4.1.0-040100rc2-generic cryptsetup: WARNING: failed to detect canonical device of overlay cryptsetup: WARNING: could not determine root device from /etc/fstab ln: failed to create symbolic link ‘/root/lib/systemd/system/cdrom.mount’: No such file or directory run-parts: executing /etc/kernel/postinst.d/pm-utils 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic Errors were encountered while processing: linux-headers-4.1.0-040100rc2-generic ubuntu@ubuntu:~/Downloads$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Christopher Sorry for need more clarification. 1. Which version of usb boot Ubuntu distribution I should use as base kernel, before update mainline kernel? Currently I have 15.04 dailybuid, and 14.04.2 LTS. (on mobile so can't download more new distribution at the moment) Or if you want particular base version, please send the link. 2. The usb boot ubuntu is Read Only, how do I make new mainline kernel to be install on to the usb boot ubuntu. I did try to install .deb but it has error and said not enough space also some error saying read only directory. So I recreated the usb 15.04 dailybuild to test again. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Christopher 1st question So what we hope, so call bug fixed is " after installation of the upstream Kernel and reboot", >>>the F2 and F12 will be available to user immediately,< 2nd question. Do you know which software is responsible for UEFI installation part? I suspect if the problems of fastboot was turned on or Bios hacked or whatever to effect the F2 and F12 boot menu fuction, we should try that installation software. Sorry I don't have the knowledge of The kernel UEFI, if The access of the Bios is part of the Kernel.? But I saw grub was installed in the "Bios" EEPROM or some kind of memory on board for UEFI boot soft ware. Since I remove Hard Disk and found Grub menu instead of the Bios. And the F2 and F12 are not there any longer. So please help identify the software that modify the UEFI-Grub as well. the issue may lie there. I will help test those new versions of these software and see if it will wreck the bios. Thank You -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Christopher Please confirm that, I just use the current installed Ubuntu 15.04 (with current Wrecked Bios that cannot access both F2 Bios Setup nor F12 boot menu) and just use these .deb to update Kernel using ubuntu software center, http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc2-vivid/ linux-headers-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392382/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
apport information ** Tags added: vivid ** Description changed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 16:57:39 2015 InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut1480 F pulseaudio rut7079 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1F dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU + --- + ApportVersion: 2.17.2-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rut2207 F pulseaudio + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=8fd2670c-4060-4d14-8f27-b9f806fe2ce7 + InstallationDate: Installed on 2015-05-06 (0 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + MachineType: FUJITSU LIFEBOOK LH532 + Package: linux (not installed) + ProcFB: + 0 inteldrmfb + 1 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=3129a485-81a2-48ef-be95-ef9c9a57be3e ro quiet splash + ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.19.0-15-generic N/A + linux-backports-modules-3.19.0-15-generic N/A + linux-firmware 1.143 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: vivid + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 05/24/2012 + dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. + dmi.bios.version: Version 1.10 + dmi.board.name: FJNBB1F + dmi.board.vendor: FUJITSU + dmi.chassis.type: 10 + dmi.chassis.vendor: FUJITSU + dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: + dmi.product.name: LIFEBOOK LH532 + dmi.sys.vendor: FUJITSU ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392367/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/lis
[Bug 1451387] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392381/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392380/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392368/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392379/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392375/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392370/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392377/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392378/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392372/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392371/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4392369/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Christopher I use ubuntu 15.04 Daily build 1. After installing on MBR-1TB works fine and still intact my fixed F12 Boot Menu 2. Use Gpart to convert the hdd to GPT partition type, empty though. 3. After installing on GPT-UEFI 1TB, Ubuntu loaded fine, BUT F12 Boot Menu disappear again and F2 is still missing as before So not yet fix. What to do next. I am still in the disaster mode, no Bios F2 nor F12 Boot Menu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Christopher, I had a long chat with Fujitsu Technician who fix somany LH532 in Thailand, which sold with no OS and Ubuntu destroy Bios. Unfortunately the Warranty has expired and there for they don't need to support them any longer. They delete the Bios files for the reason they don't want to have anything to do with that problems any longer. And warn that even in Thailand they sold a few models. The Bios is for preinstall Widows OS will be different than Bios version with no OS, even though they have the "same version no."/ If you have the wrong version burn into the Bios Chip, you will have a dead main board, and they did have the dead ones before they learn that. With those problems, Fujitsu decide to remove Bios download from the public websites, at least for Asia-Pacific region, and I could not find them for the US and Canada also. And we are left in Cold. The technician has opinion that it was Ubuntu that Block the use of F2 and F12 functions. So who ever wrote those parts of the Ubuntu installaion routine, should revise what they have done. You cannot blame Fujitsu, these robust notebook, did not break and UBUNTU hack into their Bios and stuff it up. He also warn that Fujitsu will not honour any warranty if it found their Bios is tampered with. And they stop selling the non OS notebook, only preinstalled window 8 with GPT partitions only. And If we change that to MBR and installed other OS, Fujitsu Technician said that will also void the warranty. It means If I bought new Fujitsu ( I am about to do that) we will be risking void the warranty, and the Fujitsu Technicians confirm, they are not supplied with Bios for new models at all. (The main factory don't want them to mess up the mainboard again while under Warranty.) So they could not help us fix the Bios problems any longer. He also confirmed that by removing CMOS batteries for LH 532 . I will reset only the date, not the Bios settings. And only the CL1 AND CL2 short circuit is the only way to get the F12 BACK. Now I hope those Kernel or grup or iNSTALLATION team GURUs will try to fgure out. How to unblock the work that they hack into Fujitsu Bios or their UEFI manipulation. = I will reformat MBR 1TB and install 15.04 as you instructed. I will later do GPT 1TB, it may be 2 days now before I could finish all these testiong, since holiday is over in Thailand today. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
http://support.ts.fujitsu.com/Download/ShowFiles.asp is for the following 2 series LIFEBOOK LH532 (UMA) serial no. DQBAx LIFEBOOK LH532/G22serial no. YLKFx UMA has latest updated version 1.1 G22 has latest 2.06 mine was bought in Thailand and the support site is http://www.fujitsu-pc-asia.com/driversupport/selectioninterface/selection.html# which has no bios update at all. and my serial no. start with 57544B-. On Wednesday, at the moment is a long holiday, I will contact fujitsu Thailand and see if they could help with the latest bios. for today at this moment. sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date Version 1.10 05/24/2012 -- I will look forward to get new updated bios installed. And I will follow your instructions. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
Dear Christopher. I could redo the GPT-UEFI installation of Ubuntu 14.04.2 as it did wreck the F12 boot menu the second time. I have now short circuit Cl1 and Cl2 twice now. But I will do it only when you instruct me to do so. I have to go out now be back in 4 - hours or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390609/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390610/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390611/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390603/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390605/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390607/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390606/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390599/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390600/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390602/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
apport information ** Tags added: apport-collected ** Description changed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 16:57:39 2015 InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rut1480 F pulseaudio + rut7079 F pulseaudio + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b + InstallationDate: Installed on 2010-01-01 (1949 days ago) + InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) + MachineType: FUJITSU LIFEBOOK LH532 + Package: linux (not installed) + ProcFB: + 0 inteldrmfb + 1 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.16.0-30-generic N/A + linux-backports-modules-3.16.0-30-generic N/A + linux-firmware 1.127.11 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: trusty + Uname: Linux 3.16.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 05/24/2012 + dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. + dmi.bios.version: Version 1.10 + dmi.board.name: FJNBB1F + dmi.board.vendor: FUJITSU + dmi.chassis.type: 10 + dmi.chassis.vendor: FUJITSU + dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: + dmi.product.name: LIFEBOOK LH532 + dmi.sys.vendor: FUJITSU ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390598/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390608/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390601/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1451387/+attachment/4390604/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] [NEW] Ubuntu UEFI install locks out UEFI firmware
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 16:57:39 2015 InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: Ubuntu UEFI install locks out UEFI firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
Please let me know what kind of report you need to get from us. I am sending "ubuntu-bug report" under present MBR 1 TB installation. https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1451387 Do you want me to do Ubuntu Installation with GPT-UEFI and file another terminal bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
If we need to be in GPT-UEFI installation ( that crippled F2 Bios and F12 Boot Menu ) to creat the "ubuntu-bug report", I would redone it again when I have more free time. Also I will do the ubuntu-bug report afterward in the MBR 1 TB installation. So please confirm if that excersise will help the debuging team. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
I have now got MBR 1TB ubuntu installation. Is it worth to file that "ubuntu-bug linux" ? Since only the Bios need to be flashed. And the report would not show the Bios problems, would it shows? And the F12 Boot Menu is working perfectly now. My concern for the reporting are, 1. david6's work around is not working for me and I spent 4 hours upgrading that 14.10, so I hope he response with more details. So others will not spend their times on the wrong path. 2. My fix and workaround aren't mention anywhere so I hope this will hellp others to at least stop further repeated problems. Though they may not be able to flash Bios, like me. 3. Make proposal to "ubuntu installation programing team" to imporove user's warning and alternative workaround options. Please suggest is this the place to voice opinion on this matter. Thanks. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
Please look at my post in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 >> My Fix and workaround.<<< In short process. 1. Short circuit CL1 and CL2 as posts above, to get F12 boot menu. 2. Boot with live Ubuntu then convert GPT 1TB to MBR 1TB (using gdisk) 3. Install Ubuntu on one of the partition of MBR 1TB, (I made 6 partitions). Result = multi boots ubuntu no more F12 boot menu wrecking. Now I can install Windows and other Ubuntu derivertives, no issue on usb nor DVD boot choices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273060 Title: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
I have Lifebook LH532 and for almost 2 years not a problems with EFI boot (installed ubuntu(&derivertives multi boots) more than 20 times) until I upgrade 750GB (MSDOS) with new empty 1TB (was formated to MBR-MsDos) and installed ubuntu 14.04.1 as only OS in 1TB and let ubuntu did that automatically, (1st choice installation) it made 1TB as GPT and did UEFI installation. Ubuntu 14.04.1 hacked and blocked firmware Bios, no more F2 Bios option and F12 boot menu. Yes I confirm as this bug and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060 - I have upgrade ubuntu 14.04.1 installation to 14.10 reboot and try to do what david6 (andrew-dowden) wrote on 2015-04-13: said above. Press produce only to interupt grub boot menu to grub> (grub promt) So it is not workaround for me at the moment. david6 please explain details of what your procedures and the end results please. I have not tried fresh install Ubuntu 14.10 === >> My Fix and workaround.<<< In short process. 1. Short circuit CL1 and CL2 as posts above, to get F12 boot menu. 2. Boot with live Ubuntu then convert GPT 1TB to MBR 1TB (using gdisk) 3. Install Ubuntu on one of the partition of MBR 1TB, (I made 6 partitions). Result = multi boots ubuntu no more F12 boot menu wrecking. Now I can install Windows and other Ubuntu derivertives, no issue on usb nor DVD boot choices. Conclusion >>> Don't allow your harddisk to be made to GPT before ubuntu installations. if you are not 100% that your BIOS is compatible with Ubuntu GPT-UEFI installation., By forcing your harddisk to be MBR or MSdos format, before Ubuntu installation. That prevent UBUNTU to be installed in GPT-UEFI that can wreck your Bios. (And do not allow Ubuntu to install in the first choice, by UBUNTU's ways, you must select the last option, choose your own ways of installations.) I have not flash Bios since mine LifeBook was bought in Thailand and those above links are UK models. So I did not dare to flash Bios yet. But I can install the same Ubuntu 14.04.1 many times without wrecking F12 boot menu any longer. for newbies to ubuntu So It is the GPT of the harddisk that force Ubuntu to install as UEFI mode and wreck Fujitsu Bios. It is the "worst bug" (from user point of view) I found on Ubuntu for my life. Ubuntu GURUs must do somethings. This give bad names to ubuntu. The computer technician quote $100 to fix my Bios. = Propose simple problems reductions or preventive solutions (for under 2TB Disk). 1. During Installation, there must be warning message about making harddisk into GPT partition type with " very prominent LETTERING " that this GPT and UEFI installation could wreck the Bios of your computer. (Many computer's Bios are not compatible with UBUNTU UEFI installation and result in blocking further use of Bios, and with samples models Fujitsu and many others.) "Proceed with your own risk " or "Choose to do the MBR and Bios installation option." then safe old days of installations are done. 2. The installation process check the troblesome models of computers and just force Bios-MBR installations for those troblesome machines in the only Bios-MBR lists. But perhaps it should have the option of EXPERT MODE that can override this forced Bios-MBR installation. = Propose alternative solution. Request to the UBUNTU and Grup Gurus to do the Smart Grup "Auto Boot Menu" Regardless of UEFI successful installations or not. Grup will install an auto detect boot media and creat options for user to boot from the choices as those provided by the Bios. So we don't have to fix the bugs immediatly but user can carry on their other installation choices. But the Bios will be wrecked still. So the previous proposals should be in placed as well. = Thanks every one who try to help our communities. And I hope the Guru will fix this bug soon. ** Changed in: shim (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827669] Re: [138a:0018] Validity Sensors fingerprint reader not recognized
Also affecting HP dv6-6137tx Bus 001 Device 003: ID 138a:0018 Validity Sensors, Inc. Ubuntu Release 12.04.1 (precise) 64-bit, Kernel Linux 3.2.0-36-generic According to https://launchpad.net/~fingerprint/+archive/fprint no support for 138a:0018 only the 138a:0008 Any one have a success with 138a:0018 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827669 Title: [138a:0018] Validity Sensors fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/827669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030715] Re: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems
Any one help on this report please do so at The link is https://bugs.launchpad.net/ubuntu/+source/grub- installer/+bug/1030772 ADMIN please see if I should close this bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030715 Title: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030772] Re: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation
http://ubuntuforums.org/showpost.php?p=8716089&postcount=1 is another instruction to install btrf. I believe that the errors are normal result of the wrong way of installation of btrf file system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030772 Title: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030772] Re: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation
From https://help.ubuntu.com/community/btrfs ... You must install it to either the parent (sda rather than sda1; MBR/Reserved Sectors) 'OR' use a dedicated /boot partition as described in the forum post below. When installing Ubuntu in one large btrfs-Partition without an extra boot-partition, take care to keep about 1 Mib space free at the beginning of the disk. When there is not this space, the installer fails at the end when trying to install Grub! And https://btrfs.wiki.kernel.org/index.php/Ubuntu_support ..long and involve good understanding of btrf. and how to That is not an easy normal installation of ext4... I just learn that today after reading many more info on how to btrf? Can someone confirm the above issue. That I am too naive to just select the btrf in replacement of ext4, during the normal installation. Because if we want to use btrf we need to follow these instructions in https://btrfs.wiki.kernel.org/index.php/Ubuntu_support or it is another bug in the 12.04.1 installation programs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030772 Title: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030715] Re: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems
Also more on installation of btrf. http://ubuntuforums.org/showpost.php?p=8716089&postcount=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030715 Title: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030772] Re: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation
I used the same Ubuntu 12.04.1 Live USB stick, installed to the same partition sda12 with ext4 as file system. No errors and result in 100% perfect Ubuntu 12.04.1 that I use to write this report. https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030715 was generate by Live DVD Ubuntu 12.04.1 that crashed as I choose btrf as file system, The reboot to hard disk result in grub rescue prompt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030772 Title: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030715] Re: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems
This bug report was done by autoreport during installation Live DVD crash. I have the same crash but installed by Live USB. The link is https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772 I think I identified the condition. Which is I choose btrf file system instead of ext4 at the installation instruction. Please look at details at bug report in the above link. I test reinstall Ubuntu 12.04.1 with the same DVD and choose ext4 to the same partition sda12, with 100% positive success. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030715 Title: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030772] Re: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030772 Title: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030772] [NEW] btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation
Public bug reported: This is second time identical Grub installation EROR and termination of installation. Both with Live DVD, which I report in about 1 hour ago. This time I use Live USB, complete clean booted in to Desktop with no error. Then I execute installation and choose btrf file system as root partition or install partition. I think it is the btrf option that crash the installation. Since I have reinstall (using Live DVD 12.04.1) to sda12 with ext4 with 100% perfect, test boot into new hard disk installation. I will reinstall with Live USB with ext4 installation, and report back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.18 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 CasperVersion: 1.315 Date: Tue Jul 31 04:17:32 2012 InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120727) ProcEnviron: LANGUAGE=en_AU.UTF-8 TERM=unknown PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubiquity-2.10.18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030772 Title: btrf file system was selected as root partitions (Live USB). produce the same bug report as Live DVD installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030715] Re: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems
I have execute Check Disk for Error before installation. No error on the DVD report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030715 Title: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030715] Re: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030715 Title: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030715] [NEW] 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems
Public bug reported: After download 12.04.1 I use in Live USB installed 2 times. now I test with same iso image, but burn to DVD and this is the first "Live" then installation. I will try again after this report, both usb and Dvd go into "Live" mode(try Ubuntu) first before order installation. will give feed back ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.18 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 CasperVersion: 1.315 Date: Tue Jul 31 00:48:02 2012 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- LiveMediaBuild: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120727) ProcEnviron: LANGUAGE=en_AU.UTF-8 TERM=unknown PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubiquity-2.10.18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030715 Title: 12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995126] Re: 12.04 (i386) installer crashes after "import account" wizard
I have installed Quantal 12.10 (20120727.1). it is good, no error, Well No Migration menu at all. So no bugs. confirm 28 July 2012 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995126 Title: 12.04 (i386) installer crashes after "import account" wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/995126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995126] Re: 12.04 (i386) installer crashes after "import account" wizard
Update 28 july 2012 New Ubuntu 12.04.1 LTS (built 20120727) solve this bug. I have tested new 12.04.01 LTS in the same environment as 12.04 LTS. No menu come up for "migrating of your old account" at all, so no issue for that bug. Great work, that is worth while for me to spend days to identified this bug. I will be testing Quantal after this post. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995126 Title: 12.04 (i386) installer crashes after "import account" wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/995126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998492] Re: Fails to detect package download errors on architectures other than amd64
Try installation again and exact crash at the end after userid and password config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998492 Title: Fails to detect package download errors on architectures other than amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/998492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998492] Re: Fails to detect package download errors on architectures other than amd64
Crash after key in user id and password. I have full functioning and full update Ubuntu 12.04 on external usb hard disk Fujisu 400 GB. I installed ubiguity to the installed Ubuntu 12.04. Reboot, and boot into Ubuntu 1204 and start installation to the main notebook hard disk sda13 (seagate 300 gb) It crashed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998492 Title: Fails to detect package download errors on architectures other than amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/998492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995126] Re: 12.04 (i386) installer crashes after "import account" wizard
details of error screen shots for my problems abover are in http://ubuntuforums.org/showthread.php?t=2032652 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995126 Title: 12.04 (i386) installer crashes after "import account" wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/995126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995126] Re: 12.04 (i386) installer crashes after "import account" wizard
I have test more installation, got 2 syslog attached one on 23 July (I will include 17 July next post) I had screen shorts recorded the error pages too, if the Gurus need to see. (I got that when I try to install from booted sda3 12.04 to my sda12 as a second ubuntu 12.04 in my note book. It report migration-assistant cannot unmounted sda3, I have to click go back button, it will exit the installation at this point and report error while migrating data (though I did not click the sda3 for import at all, and always) Then it gave successful installation and ask us to reboot. It fail to reinstall grub, so you will end up with old grub menu. I found work around this grub update error by 1. Installing Boot Repair in the USB live and use Boot Repair to update Grub that has option to boot into new "fail" Unbuntu 12.04 installation. 2. I boot into existing "Good" Ubuntu partition and use Grub Customiser to write to MBR the new update with new"fail" Ubuntu 12.04 installation (Boot Repair did not allow us to update grub, it told me to do the no.1 so I did that successfully) The "fail" ubuntu 12.04 after this work around perform well with no sign of crippled Ubuntu. I can install many other programs including Epson TX series and use it perfectly. Wifi function ok. I would say 100% working. ** Attachment added: "syslogJuly23" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/995126/+attachment/3234172/+files/syslogJuly23 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995126 Title: 12.04 (i386) installer crashes after "import account" wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/995126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995126] Re: 12.04 (i386) installer crashes after "import account" wizard
I installed 12.04 from CD it also failed at the same point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995126 Title: 12.04 (i386) installer crashes after "import account" wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/995126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995126] Re: 12.04 (i386) installer crashes after "import account" wizard
I would like to confirm crash after "importing account" toward the end of the installation process. I have 5 fail installation. My hardware is Hp Dv1729TU (dv1000 series) The first installation of 12.04 is ok. The later installations in the another partition always display existing partitions, and ask if we want to import the settings. I always did not check or choose any account. But it always report problems with importing and stop with successful installation note. (But in fact it is not). I installed Ubuntu 10.04 after that to see if it is my machine or what. Ubuntu 10.04 and Fedora 17 installation are perfect. Try 12.04 2 more times, the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995126 Title: 12.04 (i386) installer crashes after "import account" wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/995126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991110] Re: [Aspire 3830T, Conexant CX20588, Speaker, Internal] No sound at all
https://answers.launchpad.net/ubuntu/+source/alsa- driver/+question/202340 Eva has it solved. His sound is working now. Please try his ways and see if it solve your problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991110 Title: [Aspire 3830T, Conexant CX20588, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/991110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898655] Re: grub-install trashed grub-menu if run on current partition to make current partition to be a default boot up OS
I have SOLVED the above problems #1 by using boot-repair to do install grub2 so we can set the default boot OS to the "current" partition we are booting from. Notes for Newbies = You can install "boot-repair" as in https://help.ubuntu.com/community/Boot-Repair and use that "boot-repair" instead of "sudo grub-install .." BUT YOU MUST, 1. READ the whole page thoroughly. 2. You must click on Advance Option and MAKE SURE you select the correct /dev/sd?? = So I think we must execute more commands to make sure it can be done as "boot-repair" can do. But if we execute just the above commands as #1 post, from other partitions or drives it worked successfully. So I still consider it is a "Reports" Bugs still. Dear Gurus, please help to comment and teach us how to do it properly, if the above is considered not a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898655 Title: grub-install trashed grub-menu if run on current partition to make current partition to be a default boot up OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/898655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
I would like to confirm that my above experiences with grub-install and boot-repair on the troublesome ".Sector 50 is already in use by FlexNet..." has actually fixed the bugs, and no problems with any ntfs partions at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
Please remove all my above posts from this thread, if you belive it is out of context. since it has nothing to do to "grub-install trashes the ntfs partition" and nothing to do with the ".Sector 50 is already in use by FlexNet..." as I thought at the beginning. Because I found in later experiments that "grub-install trashed grub-menu if run on current partition to make current partition to be a default boot up OS" So I have decided to start report this bug at https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/898655 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898655] Re: grub-install trashed grub-menu if run on current partition to make current partition to be a default boot up OS
** Summary changed: - grub-install trashed grub-menu if run on current partition to reinstall current partition to default boot up + grub-install trashed grub-menu if run on current partition to make current partition to be a default boot up OS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898655 Title: grub-install trashed grub-menu if run on current partition to make current partition to be a default boot up OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/898655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898655] [NEW] grub-install trashed grub-menu if run on current partition to reinstall current partition to default boot up
Public bug reported: Please see the note at the end for why I start this bug report. --- The bugs apply to both grub versions, with full updated all packages to the most current date, 2 Dec 2011 tbuntu@tbuntu:~$ grub-install -v grub-install (GRUB) 1.99~rc1-13ubuntu3 Ubuntu 11.04 and tbuntu@tbuntu:~$ grub-install -v grub-install (GRUB) 1.99-12ubuntu5 Lubuntu 11.10 - grub-install will destroy "grub boot menu" and you will get "grub command prompt", if you use the command grub-install in the following ways you boot into "current partition", in my case sda4 contain ubuntu 11.04 (I also test with the same result in Lubuntu 11.10 in /dev/sda11) sudo mount /dev/sda(current partition) /mnt in my case sudo mount /dev/sda4 /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sda in my case I want to reinstall grub to /dev/sda so when the computer boot up it will auto boot into sda4, which is the ubuntu partition I am using, "to execute" the grub-install command. It will produce this message. "Installation finished. No error reported." But in fact the grub menu was "trashed" or "disabled", after you reboot, it will only be a grub> display. My opinion the bugs are 1. The "report-Installation finished. No error reported." at the end is wrong information. or / and 2. If usage of the above "grub-install" is prohibited, then grub-install should refuse to continue and there should be an error message telling you cannot "do grub-install" to your "current" partition. -- Notes: 1.) I have commented in the https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225 since I thought the error I got ..Sector 50 is already in use by FlexNet; avoiding it... was the main cause for destroyed grub menu. and that bug report is the same as mine. But after experiment with clean hard disk that produce no "...sector 50...Flexnet". it resulted in the same "destroyed grub menu". So I decide to report as bug. 2.) the reasons I start to do grub-install the above way, because the "startup-manager" fail to change grub menu as it did for my other previous Ubuntu versions, for my Lubuntu 11.10 to be a default boot OS. So I accidentally found that later that it is a bug? ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898655 Title: grub-install trashed grub-menu if run on current partition to reinstall current partition to default boot up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/898655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
I don't know if we do not have "Sector 50 is already in use by FlexNet" can we do grub-install from the current partition of root (and boot) to force it's partition to be default boot partition. I don't dare to do "dd" command to try to delete that "Sector 50" so I get stuck here for the time being. if anyone knows or have different result please comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
It is confirm after 6 times of grub-install with the error "Sector 50 is already in use by FlexNet", 1. you can successfully reinstall grub only if you use - usb live cd ubuntu or other installed ubuntu partitions. with exact the same messages as No.2 /usr/sbin/grub-setup: warn: Sector 50 is already in use by FlexNet; avoiding it. This software may cause boot or other problems in future. Please ask its authors not to store data in the boot track. Installation finished. No error reported. 2. grub-install will destroy "grub boot menu" and you will get "grub command prompt", if you use the command grub-install in the following ways you boot into "current partition", in my case sda4 contain ubuntu 11.04 (I also test with the same result in Lubuntu 11.10) sudo mount /dev/sda(current partition) /mnt in my case sudo mount /dev/sda4 /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sda in my case I want to reinstall grub to sda4 so when the computer boot up it will auto boot into sda4, which is the ubuntu partition I am using to execute the grub-install command. It will produce this message. - /usr/sbin/grub-setup: warn: Sector 50 is already in use by FlexNet; avoiding it. This software may cause boot or other problems in future. Please ask its authors not to store data in the boot track. Installation finished. No error reported. you will get grub> and not your grub menu any longer. I don't know "if I should post this as new bug or not". But certainly it is not correct when grub report "No error reported". And you will get a "destroyed grub menu" after reboot. note== the reasons I start to do grub-install from Lubuntu 11.10 to force grub to start Lubuntu 11.10 as default os. because the "startup-manager" fail to change grub menu as it did for previous version. which I don't know why, bugs or just incompatible grub version in sda. But the above "bugs" I have tested and found to be on both Ubuntu 10.04 and Lubuntu 11.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
with the same hard disk, I use usb stick Ubuntu 11.04, install boot-repair, use boot-repair to reinstall grub2 to the sda. with sellection to default boot in to Lubuntu 11.10 Successful re-installation and no error message. Successful boot into Lubuntu 11.10 on sda11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
But for Windows XP dual boot. After successful fresh install of Ubuntu 11.04, Grub has no problems to start my windows XP. Only the main Grub Menu was destroyed. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
Disaster, It actually destroy Grub, reboot went into grub rescue command, grub> I fresh install Ubuntu 11.04 to sda4. Successful installation and boot with all grub options correctly listed. The root partition is in sda4, I test the same command, --- tbuntu@tbuntu:~$ sudo mount /dev/sda4 /mnt [sudo] password for tbuntu: tbuntu@tbuntu:~$ sudo grub-install --boot-directory=/mnt/boot /dev/sda /usr/sbin/grub-setup: warn: Sector 50 is already in use by FlexNet; avoiding it. This software may cause boot or other problems in future. Please ask its authors not to store data in the boot track. Installation finished. No error reported. tbuntu@tbuntu:~$ grub-install -v grub-install (GRUB) 1.99~rc1-13ubuntu3 --- grub is destroyed, and it will go to grub rescue again == How ever I used exact same command form live usb hardisk, It produce the same error tbuntu@tbuntu:~$ sudo mount /dev/sda4 /mnt [sudo] password for tbuntu: tbuntu@tbuntu:~$ sudo grub-install --boot-directory=/mnt/boot /dev/sda /usr/sbin/grub-setup: warn: Sector 50 is already in use by FlexNet; avoiding it. This software may cause boot or other problems in future. Please ask its authors not to store data in the boot track. Installation finished. No error reported. But this time successful grub re installation. It may be because I am in the root partition and I should not mount /dev/sda4 or sda11 when using as root in that partition. How ever grub should not produce the same reports for the unsuccessful installation. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878294] Re: external USB disk freezes PC when unmounted
I do confirm now after more than 15 times. With new update initrd.img-3.0.0-13-generic no problems any more. Problems solved with later kernel update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878294 Title: external USB disk freezes PC when unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/878294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730225] Re: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet
I have reinstall grub in my note book many times and no "error message" like this one, - tbuntu@tbuntu:~$ sudo mount /dev/sda11 /mnt [sudo] password for tbuntu: tbuntu@tbuntu:~$ sudo grub-install --boot-directory=/mnt/boot /dev/sda /usr/sbin/grub-setup: warn: Sector 50 is already in use by FlexNet; avoiding it. This software may cause boot or other problems in future. Please ask its authors not to store data in the boot track. Installation finished. No error reported. tbuntu@tbuntu:~$ grub-install -v grub-install (GRUB) 1.99-12ubuntu5 - I will see if my window XP is destroyed or not. I have Ubuntu 10.04, 11.04 and Lubuntu 11.10 installed with window XP. The previous grub reinstall was done in Ubuntu 11.04. And after that I did experiment with Boot Repair, and set Ubuntu 11.04 as default boot. Current Lubuntu 11.10 (sda11) was a clone of Lubuntu 11.10 (sad4) by Clonezilla CD, my first experiment on Cloning by Clonezilla. Then I format sda4 for next ubuntu installation. And after that I did experiment with Boot Repair, and set Ubuntu 11.04 as default boot. And today, I reinstall grub2 since I want default /boot to be change to lubuntu 11.10(sad11). Then I have the above error. I have not install any new adobe software in windows at all for long time, and the last time I turn on my windows, to check window files system of usb-hdd. and did not update anything. The only Adobe program is AR Reader installations were done to USB-stick Ubuntu, or external drive and to some of my Ubuntu experiment. Though Photoshop and AI and other Adobe update in windows XP were done years ago, since I install Ubuntu 8.04, and never have this issue until lubuntu 11.10 "grub reinstall". The installation of lubuntu 11.10 did not produce any error too. When Bug Watch Updater (bug-watch-updater) on 2011-03-16 Changed in grub2 (Debian): status: New → Fix Released Dose it suppose to still produce the error above? I will report on my XP later. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730225 Title: grub-install trashes the ntfs partition that starts at sector 63 if one or more sectors in the embedding area is occupied by Adobe FlexNet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/730225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878294] Re: external USB disk freezes PC when unmounted
I update every thing, enable preleased and unupdate in Software Souce / update and update everything, initrd.img-3.0.0-13-generic was installed and it is fixed, Nividia is runing ok too. But i had 2 unsuccesful boots. the mouse freeze and another time everything freeze, but other times here give report. Now I cannot boot into initrd.img-3.0.0-12-generic original nor the above initrd.img-3.0.6-generic. They all freeze at black purple screen, only initrd.img-3.0.0-13-generic seem to give me a chance to go on to normal Ubuntu. I will do new clean reinstall and update and will report back when I got time to night. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878294 Title: external USB disk freezes PC when unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/878294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878294] Re: external USB disk freezes PC when unmounted
New kernel 3.0.6 gave me one new problem? I cannot install Nvidia Driver, try a few seach solutions, still error when try to install Nividia driver. But the "Freeze" problems when" safely remove drive" seem to be fixed. But the graphic resolution got thrown back to standard resolution, and lost Nvidia seting option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878294 Title: external USB disk freezes PC when unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/878294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878294] Re: external USB disk freezes PC when unmounted
yes "Upgrading to 3.0.6 kernel has fixed this for me; http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.6-oneiric/ " works for my desktop, solve the problems. I will try on my server, which crashed and broke Raid Drives immediately when I mouse click on "saftly remove drive". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878294 Title: external USB disk freezes PC when unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/878294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881465] [NEW] ubuntu 11.10 crash at the end of installation with mdadm raid setup
Public bug reported: Install finish with error installing grub into /dev/sda which is under mdadm md0 config raid=0 it comprise of 2 x 60 GB SSD drive , sda = sda1-16 GB-swap + sd2-44 GB , sdb = sdb1 60GB, md0 is format with ext4 with /. md0 = sda2 +sdb1 = 103 GB md1 (raid=1 , mirror) = sdc-2TB + sdd-2TB, is format with ext4 with /home = 2TB error cannot install grub on /dev/sda it will not continue with any installation of grub to other /dev/sd?? or /dev/md??, will return the same error of error cannot install grub on /dev/sda and it will not continue even select "option - continue with out installing boot loader" so I click "X" on top left conner to close the error window, and it ask me to help report , so I am here. the installation complete hung up with disabled "Continue Testing" it highlight only "Restart Now" which I don't dare to click as yet. Since I want to finish reports to u. Best Regards to all the gurus. aimwin ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: ubiquity 2.8.7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CasperVersion: 1.287 Date: Wed Oct 26 01:31:25 2011 LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_AU.UTF-8 PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric ubiquity-2.8.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881465 Title: ubuntu 11.10 crash at the end of installation with mdadm raid setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/881465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881465] Re: ubuntu 11.10 crash at the end of installation with mdadm raid setup
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881465 Title: ubuntu 11.10 crash at the end of installation with mdadm raid setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/881465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 671403] Re: Ubiquity installer crash while installing from an already installed Ubuntu 10.10 notebook harddisk
** Attachment added: "syslogNpartmanNinstallerErrorNsysinfoMB.tar.gz" https://bugs.launchpad.net/bugs/671403/+attachment/1723857/+files/syslogNpartmanNinstallerErrorNsysinfoMB.tar.gz -- Ubiquity installer crash while installing from an already installed Ubuntu 10.10 notebook harddisk https://bugs.launchpad.net/bugs/671403 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 671403] [NEW] Ubiquity installer crash while installing from an already installed Ubuntu 10.10 notebook harddisk
Public bug reported: Binary package hint: ubiquity Ubiquity installer crash while installing from an already installed Ubuntu 10.10 I am trying to install ubuntu 10.10 to usb hard drive, /dev/sdb2 which is sumsung (SV200IH) 20GB in usb external hard disk enclosure with SATA&IDE dual interface. This is first time I try to do "Install RELEASE" from my notebook hardisk Ubuntu 10.10. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: 10.10 bug crashed in install installer release ubuntu -- Ubiquity installer crash while installing from an already installed Ubuntu 10.10 notebook harddisk https://bugs.launchpad.net/bugs/671403 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 530554] Re: video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid
I finally found another easy way to work around to get high resolution 1152 x 864 (4:3) 1. After power up. At GNU GRUB menu, choose "recovery mode" choice, 2. Wait until it load the new menu, scroll down to pick the choice load with safe mode graphic, don't press enter yet, go to next step. 3. very important turn off your monitor, obviously this doesn't apply to Notebook. 4. then press enter key, and wait for two minutes or so. 5. turn on the monitor, hopefully you should see the mouse pointer smaller then before (in higher resolution). 6. just choose the choice to reconfigure graphic card now and choose restart x server. 7. I hope you got a higher resolution than what your default boot will make it for you. 8. I managed to have continue high resolution now, almost every time, when I turn on my computer. BUT I HAVE TO LEAVE MONITOR TURN OFF until Ubuntu has fully loaded 2-4 minutes depend on your hardware. If you failed to do so, start step 1 again. Dear Gurus of Ubuntu 1. I am willing to try anything to have a permanent fix. So I will post to http://ubuntuforums.org/showthread.php?p=9231489 2. If you have newer version of Lucid for me to try let me know, I will help to see if we can improve our Lucid. Thank you -- video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid https://bugs.launchpad.net/bugs/530554 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351882] Re: [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure
No #8 post is for Asus P4S800-MX SE desktop Please see attached file for Sysinfo file. to look at other print out please look at post #8 on SIShigresolution.tar.gz with below link https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/530554/comments/9 ** Attachment added: "sysinfo" http://launchpadlibrarian.net/47616992/sysinfo -- [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure https://bugs.launchpad.net/bugs/351882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351882] Re: [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure
Dear Madam, Sir My previous post #7 was wrong, the matter is for my Asus note book not for Asus P4S800-MX SE desktop. I have now installed Lucid 30/04/2010. I have problem with suspend and hibernation still. Suspend: I will go on suspend, the power led will keep blinking, And the power supply was actually turn off. I need to press power button, and wait a few minutes, then press arrow key to wake up to log in screen, after enter password, it went to desk top OK. It returned to full function with out problems. Hibernation: It will randomly work with fresh boot then load Firefox then Hibernation. Many times it will not work, and Ethernet card will be disabled. Sorry to refer to Fedora 12, this is to see if it is linux or ubuntu weakness. Fedor 12: Suspend: the same as Lucid. Hibernation: Work perfect 100% with fresh boot then load Firefox then Hibernation. Will not go to Hibernation at all if it the LAST boot was from Hibernation. Conclusion: Fedora 12 works with SIS better than Ubuntu Lucid both in High resolution and also Hibernation Please also look at problem with High resolution from Bug #530554 #7, #8, #9 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/530554/comments/9 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/530554/comments/10 I hope if you know what Fedora 12 do, if we can use the same algorithm or what ever to improve our Ubuntu and SIS chip-sets Thanks you all again Best Wish. -- [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure https://bugs.launchpad.net/bugs/351882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 530554] Re: video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid
Problems identified. Lucid hang up on first boot (or it took too long to go to desktop) >>> with new MONITOR <<< After recovery > reconfigure hardware menu in the recovery mode. The high resolution work ok with Samsung Syncmaster 913v with 1280x1024(5:4) And Lucid boot up, after a few restart, very fast, faster than on Packard Bell monitor. But suspend function worked but have to wake with power on button plus press key board, and it could hibernate but upon reboot, it will show desktop as it is fresh booted. But with network card disable. (which is the same symptom as when hibernation failed on my notebook. Fedora 12 did not fail to boot into desktop when first use this new sumsung monitor. Conclusion = XP never fail to work with Packard Bell monitor. Fedora 12 fail to have higher resolution than 900x600. But can be fool by turning the monitor off till it fully boot into Desktop. Lucid failed to do better than 900x600 but can sometimes be fool if boot Fedora 12 into high resolution first and reboot into Lucid without power off the Packard Bell monitor. I hope it will help the Gurus to improve Ubuntu with 2 days of my effort to solve the issue. -- video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid https://bugs.launchpad.net/bugs/530554 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 530554] Re: video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid
I have found: a temporary solution. -- I load LiveCD ubuntu 10.04 release 29/04/2010 with MONITOR turning OFF. After it stop (no blinking on any led) I turn on the monitor, choose "Try Ubuntu without installation" then imediatly turn off MONITOR. WAIT TILL all LED stop blinking, which mean fully loaded. Turn on the monitor, then I got high resolution. --- But After I order installation and reboot from hard disk, Lucid fail to load in higher resolution than 960 X 600. I did tried many times with, turning off the MONITOR at the same as CPU-Box computer. I waited till I think it fully boot into Ubuntu, then turn on the monitor. It failed. Then I finally tried and successfully get back higher resolution by 1. I have successfully fool Fedora 12 to load into 1152 x 864 (4:3) by 1.1 turn off computer, turn monitor off too, and turn on just computer. 1.2 Once, a few minutes, guess that you are at the Grub menu, turn on the monitor, and l pick to boot into Fedora 12 , >>> after press enter, immediately turn off monitor. 1.3 I let Fedora 12 to load completely (while leaving MONITOR OFF) 1.4 Turn on monitor and I got 1024 x 768 or 1152 x 864, I cannot remember (just so happy) but finally I set it to 1152 x 864. So it is ok with high resolution until now. 2. I fool Ubuntu 10.04 (30/04/2010 -fresh re-install from LiveCD), and no update by 2.1 After successfully fool Fedora 12 for high resolution, choose restart, (not shutdown), and do not turn off the MONITOR. 2.2 wait till it reboot into grub menu and choose to boot into Ubuntu Lucid 2.3 Yes got 1152 x 864. I have include the same kinds of files sysinfo1 > from sysinfo program lsmod, lshwCdisplay, lspciVVNN, lspci, Xorg.0.log, Xversion ---but I did not change any thing from standard installation I include these two files for comparison to the previous post. grub.cfg and modules === Conclusion for the moment. Lucid did work ok with SIS for high resolution temporary. but detection of the Packard Bell monitor made it falled back to choose lower resolution for our Lucid Hard disk installed version. Fedora can be fool with the above procedure but not Lucid. the help "is need" to make Lucid stupid like Fedora 12 So I can or may be someone else too ?? , can use SIS for higher resolution until the fixed arrive. Or the problems lies on the Packard Bell monitor ?? I will be trying with other monitor and will let you know. I am working to promote UBUNTU not Fedora, so please help. ** Attachment added: "SIShigresolution.tar.gz" http://launchpadlibrarian.net/47572189/SIShigresolution.tar.gz -- video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid https://bugs.launchpad.net/bugs/530554 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 530554] Re: video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid
I am using MOTHERBOARD Host bridge Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11) Subsystem: ASUSTeK Computer Inc. Device 8113 PCI bridge(s) Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) I can get only 960 X 600, (I use Packard Bell monitor, work with much higher resolution in XP). at maximum. And that gave me problems with many program will not display full page, it was crop off. and cannot access the apply or submit buttom, since it is out side the screen. I did accidentally got it work at 1280 X 720 some things in these range twice, The first time after I install Fedora 12 and I found it can do the high resolution, so I switch to Ubuntu 10.04, and I did not work for lucid, so I reboot back to Fedora to confirm it worked. Then reboot again to Lucid, Yes it worked. So I try to set a better resolution, and reboot. After that I cannot get it work on high resolution above 960 X 600 again, neither for Fedora 12, and it always show error message, something along these > Xorg cannot load configuration < not exact. And a few days after that it pop again with high resolution, but after reboot, never show up again. I reinstall Lucid release, to replace the RC-Lucid on 30/4/2010, hope the upstream will fix the problems, but I faced the same problems. I googled and search for many hours finally try sudo dpkg-reconfigure xserver-xorg , from one of the post, nothing happen, then I try the following http://ubuntuforums.org/showthread.php?t=1423381 and a few things from other posts. None work. So I report them here for help not for me but for all of us who has "SIS and Ubuntu" Since I want more people to use ubuntu and lots of them using SIS, I want to make sure they are happy so more people will port to ubuntu. Thank you in Advance to all the GURUs The attached files in zip, since I can find only 1 attached file button. sysinfo1 > from sysinfo program lsmod, lshwCdisplay, lspciVVNN, lspci, Xorg.0.log, Xversion also becasue of the above tutorial link, I included, grub.cfg and modules - after grub updated, ** Attachment added: "SISVGAproblem1.tar.gz" http://launchpadlibrarian.net/47293089/SISVGAproblem1.tar.gz -- video=sisfb on menu.list / grub.cfg no longer works Ubuntu Lucid https://bugs.launchpad.net/bugs/530554 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546928] Re: gnome-nettool crashed with SIGSEGV in gtk_paint_layout()
According to "Gareth Stephens wrote on 2010-04-07:#18 Also affecting me, and the previously mentioned workaround from delaneya of changing to the clear looks theme also allows the ping tab to be accessed." I did change to "Cearlooks" theme, after I filed this bug report. Then I found the last comment, change the theme to "Clearlooks", (I do nothing to the current session, no re login nor reboot, nothing..) I can use "ping tap" immediately. No Errors any more. I hope other bugs would not related to the theme we used like this bug. hope? Thanks -- gnome-nettool crashed with SIGSEGV in gtk_paint_layout() https://bugs.launchpad.net/bugs/546928 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351882] Re: [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure
My Asus P4S800-MX SE Fresh install 10.04 beta1, as at 7 April 2010 updated to System.map-2.6.32-19-generic 100% perfect - but only after select System > Administration > Hardware Drivers > "Choose NVIDIA accelerated(current version) >> then at the bottom >> activate the driver. switch use, log out, log in, suspend, hibernation, power management all function. ** all original bugs gone (thump up the new version) ** To me the above previous bugs are fixed in 10.04 beta1 / as System.map-2.6.32-19-generic / on 7 April 2010 Thanks to everyone in Ubuntu Team. BAD BAD but I am for new 10.04 any case Bad Experience with 10.04beta1 with "System.map-2.6.32-19-generic" 1. right hand part of the touch pad near vertical scroll section is not respond to finger touch properly. the pointer will jump to random spot, 2. There Plymouth clash so often especially after fresh login or turn on computer. 3. indicator applet clash randomly and 4. Once, a few days after beta1 installed (apx the end of March 2010) and updated a few times, It will not boot up into Ubuntu at all, I have to reinstall from the 10.04 beta CD. And it is fine until now. (Nothing to do with above note book but just info for developer. Second time I have bad experience 10.04beta1 - on MSI U100Plus will not boot up into Ubuntu, not even in all two recovery options available. I reinstall 10.04 beta on MSI U100Plus and I did not dare to update at all, since it work fine 100 % perfect on all sound, brightness control and camera till today though, the reason for not updating a) it is my Bank-Access working computer b) It much more perfect than previous 9.+ and 8.+ -- [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure https://bugs.launchpad.net/bugs/351882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351882] Re: [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure
Dear Developers, I herald the new function, (if you happen to build it in the Karmic) that it will not hang up, once it was instruct to suspend or hibernate, and found that the hardware doesn't accept the order. Both throw back to login screen. I wish there should be a message, saying, "We are sorry that your Hardware is not compatible for current version of Suspend or Hibernation" It will make users felt more friendly with the failure that they met. Best Wishes aimwin -- [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure https://bugs.launchpad.net/bugs/351882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351882] Re: [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure
My flesh installed 9.10 release hang and freeze computer. It did that about 5 times more, after I report above. While the hibernate and suspend still not working. I have never use other function of indicator-applet-session 0.1 except "restart" or "shutdown" ==both work fine, and the "logout" which hung up. So before I report again I start testing "switch user" , "Lock Screen" and "Guest session". All perfect 100% Then I test "logout" for the last time before I will report. It is working and perfect now. I test 5-6 times with total shut down and also restart. So far no more problems. -- [Asus P4S800-MX SE /SIS 661FX DesktopSelfBuilt] hibernate/resume failure https://bugs.launchpad.net/bugs/351882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
