[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
Forget "quiet", it's whether "fsck.mode=skip" is the last thing on the kernel command line. There is no disk check if there is something after "fsck.mode=skip". I tried "quiet". Then I tried "nomodeset" instead. I tried putting a blank at the end of the line. That was *not* enough to make the "fsck" stop the disk check. I was using the GRUB2 editor, so maybe it would have worked if I really added a blank at the end of the line in the grub.cfg file. Also, Ctrl-C does *not* abort the disk check. Given the way the display crawled through a flock of files before saying it was on squashfs, I'm pretty sure I hit the Ctrl-C before it had started on squashfs -- It just did not pay attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
I craft my boot device by hand. I'm using files filched from some
Ubuntu distribution (so, GRUB2), lately booting with the ISO file. I've
booted from an external (USB) hard disk, and from thumb drives.
On my external hard drive, I copied vmlinuz and initrd to the ESP
(because on another machine, with Secure Boot enabled, the version of
GRUB2 I filched does not support NTFS filesystems, and I cannot insert
the appropriate module). The ISO file is in a subdirectory of an NTFS
partition. The GRUB2 item is:
set bdir=(${root})/boot
set fsd=/os/boot
menuentry "Ubuntu 20.04.2 64-bit via ISO" {
set gfxpayload=keep
set ubdir=${bdir}/ubuntu200402-64
set isopath=${fsd}/ubuntu-20.04.2-desktop-amd64.iso
linux ${ubdir}/vmlinuz boot=casper iso-scan/filename=${isopath} ignore_uuid
fsck.mode=skip
initrd ${ubdir}/initrd
}
So, GRUB is told to load the kernel and initrd from the FAT-
formatted ESP, while the kernel is told to find the ISO file.
I observed the same behavior with 20.04.1 as with 20.04.2.
I observed the same behavior when booting from a thumb drive as when
booting from a hard drive.
I haven't tried to find a copy of "20.04". Was there such a thing?
Or was 20.04.1 the first released version, the one referred to in all
those posts complaining about the automatic disk check?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875548
Title:
Its not easy to determine how to skip the filesystem check
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
"fsck.mode=skip" does *not* skip disk check unless "quiet" is also on the kernel command line. Without "quiet" on the kernel command line, even with "fsck.mode=skip", I see lines flying by until it gets to the squashfs file, at which point it pauses long enough for me to read some lines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
Ubuntu 20.04.2 behaves the same way. "quiet" kernel parameter seems to enable skipping the disk check: With "quiet" on the kernel command line, one of the few lines to appear on the screen is "disk check skipped", and the boot completes noticeably faster. (35s instead of 55s, booting from an ISO file on a hard disk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
Ubuntu 20.04.1 performs the disk check when booted from an ISO. "fsck.mode=skip" does *not* prevent the disk check. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366264] Re: "Install grub to" drop down should be hidden in EFI mode
*** This bug is a duplicate of bug 1466367 *** https://bugs.launchpad.net/bugs/1466367 I think this bug may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1229488 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366264 Title: "Install grub to" drop down should be hidden in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1366264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366264] Re: "Install grub to" drop down should be hidden in EFI mode
*** This bug is a duplicate of bug 1466367 *** https://bugs.launchpad.net/bugs/1466367 This bug is NOT a duplicate of https://bugs.launchpad.net/bugs/1466367 The title of this bug should not have been changed. This bug is complaining that, when I was installing to an external drive, and I specified the ESP partition on the external drive, the installer erased the ESP partition on the external drive, and overwrote the ESP partition on the internal drive. Please tell me if I should do something to change the title back, or to dispute the current status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366264 Title: "Install grub to" drop down should be hidden in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1366264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535038] Re: iso-scan doesn't wait long enough
Bug #158976 reports a similar problem in locating the persistence file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535038 Title: iso-scan doesn't wait long enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/1535038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535038] [NEW] iso-scan doesn't wait long enough
Public bug reported: The search for the iso file doesn't wait long enough for the device to show up. In /scripts/lupin-helpers (by way of /scripts/casper-premount /20iso-scan), there is a loop that repeatedly checks a flock of devices, trying to find the specified "iso-scan/filename"-specified iso-file. The loop tries 3 times, waiting 3 seconds before the 2nd and 3rd tries. It takes about 10 seconds for my external USB drive to show up. The kernel boot parameter "rootdelay" doesn't seem to be used in a "boot=casper" context. At any rate, it isn't applied before the iso- scan. Observed in 14.04.1, and in 15.10. ** Affects: lupin (Ubuntu) Importance: Undecided Status: New ** Tags: iso-scan lupin-casper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535038 Title: iso-scan doesn't wait long enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/1535038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532663] [NEW] no debug from sub-scripts
Public bug reported: Kernel boot parameter "debug=1" produces detailed console / log- file output tracing script execution. No details are provided for the execution of sub-scripts which are run in new shells. For instance, with "debug=1" on the kernel boot command line, there are details of variable expansions tracing execution of "casper" as it calls "run_scripts" to process the "casper-premount" directory, right up to the point where it runs "/scripts/casper-premount/ORDER". It uses the shell "source" command to run ORDER, so you see some indication that there is a line in ORDER that says "/scripts/casper-premount/20iso- scan", but since this line is running iso-scan as a command, instead of running it with a "source" command, it is being run in a new shell, and the "set -x" that "init" executed as a result of the "debug=1" parameter is lost, so there are no debug messages during the execution of 20iso- scan. I realize this extends beyond casper, but I think the only safe fix will involve adding code to every sub-script to reassert "set -x" if the kernel was given a "debug" parameter. Ubuntu 14.04 ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Tags: casper debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532663 Title: no debug from sub-scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1532663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530018] Re: casper boot toram fails from USB 2.0
** Changed in: casper (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530018 Title: casper boot toram fails from USB 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1530018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530018] Re: casper boot toram fails from USB 2.0
Operator error. On the new thumb drive, I named the directories BOOT and EFI in uppercase. I used lowercase to refer to "boot" in the grub configuration. That works as long as paths refer to the FAT32-formatted thumb drive. After copying the contents of the thumb drive to the RAM filesystem, case matters. Sorry about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530018 Title: casper boot toram fails from USB 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1530018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530018] [NEW] casper boot toram fails from USB 2.0
Public bug reported: I think that when booting from a USB 2.0 thumb drive using the "toram" kernel boot parameter, the "cp" command that copies the live- media to RAM returns before the copy has completed. I am booting Ubuntu from a thumb drive. The thumb drive contains parts of Ubuntu Live-CD's. I am able to boot the 32-bit and 64-bit versions of Ubuntu 14.04 in Legacy-BIOS mode. I can boot the 64-bit version in EFI mode. When I try to boot either version of Ubuntu, in either BIOS mode, with the "toram" kernel boot parameter, the boot fails: I see the console message that it is about to copy the live-media to RAM. After about 10 seconds I get a burst of messages that look like it just rediscovered my external USB disk. After another 60 to 80 seconds of the light on the thumb drive flickering madly, I get a burst of console messages, too fast to read, ending with an "(initramfs)" prompt. The last message before the prompt says it couldn't find "/sbin/init", and maybe I should try the "init" boot parameter. From the "(initramfs)"/Busybox prompt, I can see a small set of directories (maybe the "initrd"?). There is a "/cdrom", but it's empty -- i.e., it is NOT attached to my thumb drive. There is a "/var", but no "/var/log". The only log file I can find is a "casper.log" in the "/" directory. There is a "/root" directory. It contains "/root/cdrom", on which "/dev/shm" is mounted -- this contains a complete copy of the contents of my thumb drive. I have tried adding debug print to the script "casper", checking the contents of the live-media "casper" directory on the thumb drive before the copy, and checking the contents of the corresponding directory on the tmpfs device after the copy. I tried checking again after a "sync", and again after a "sleep 100". The right files are there before the copy. Nothing seems to be there on the destination device after the copy, after the sync, or after the sleep. My main reason for thinking the "cp" command is returning too soon is the way the boot seems to proceed before the thumb drive has stopped blinking. If the burst of messages about discovering the external USB drive are coming from another process, then I don't know anything. I have another thumb drive, this one USB 3.0, with the same versions of Ubuntu. I can boot either the 32-bit or the 64-bit version in Legacy-BIOS mode, with or without the "toram" option. This is another reason I think it has to do with the speed of the USB 2.0 thumb drive. ** Affects: casper (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/1530018 Title: casper boot toram fails from USB 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1530018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530018] Re: casper boot toram fails from USB 2.0
** Attachment added: "casper.log" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1530018/+attachment/4541994/+files/casper.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530018 Title: casper boot toram fails from USB 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1530018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530018] Re: casper boot toram fails from USB 2.0
** Attachment added: "casper-patched" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1530018/+attachment/4541993/+files/casper-patched -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530018 Title: casper boot toram fails from USB 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1530018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496672] [NEW] casper check_dev bind mount directory when?
Public bug reported:
initramfs-tools/scripts/casper function check_dev will bind /cdrom
to the "device" being checked if it is a directory (and contains a
filesystem.squashfs file).
When will that "device" ever be a directory?
Bug #230716 seems to have introduced the code
if [ -d "${devname}" ]; then
mount -o bind $devname $mountpoint
if is_casper_path $mountpoint; then
echo $mountpoint
return 0
endif
fi
What I don't understand is what "devname" could be that it could be
identifying a directory, other than a directory in initrd (initramfs?),
which couldn't contain the live media.
** Affects: casper (Ubuntu)
Importance: Undecided
Status: Invalid
** Changed in: casper (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/casper/+question/271482
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496672
Title:
casper check_dev bind mount directory when?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1496672/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494123] [NEW] casper toram message typo
Public bug reported: Not enough memory (20k > 200k) to copy live-media to ram That should be a "less than", rather than a "greater than". Ubuntu 14.04 64-bit Live-DVD Unchanged as of Wily branch scripts/casper ** Affects: casper (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/1494123 Title: casper toram message typo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1494123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1474633] [NEW] Generic Text-Only driver misnamed or wrong
Public bug reported: I believe that the Generic Text-Only printer driver is either misnamed, or is not functioning correctly. The Generic Text-Only driver seems to be sending a PDF file to the printer. This is not what I expected. A driver that sends a PDF file to the printer should have a name like Generic PDF Printer. A driver named Generic Text-Only should be sending text to the printer. We can quibble about how many control codes are included in text. I think the goal for a Text-Only printer should be that printing a file from a text editor should send the same data to the printer as copying the text file directly to the printer device (cat f.txt /dev/usb/lp2). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Tue Jul 14 23:12:33 2015 InstallationDate: Installed on 2014-09-05 (313 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lpstat: device for Brother-MFC-7820N: usb://Brother/MFC-7820N?serial=000C5J505362 device for file-P1092i-on-usb: /tmp/file-P1092i-on-usb.prn device for P1092i-on-usb: parallel:/dev/usb/lp2 device for Parallel-Brother: usb://Brother/MFC-7820N?serial=000C5J505362 MachineType: Dell Inc. Inspiron One 2330 Papersize: letter PpdFiles: P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended) Brother-MFC-7820N: Brother MFC-7820N Foomatic/Postscript Parallel-Brother: Brother MFC-7820N Foomatic/Postscript file-P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=de488065-a683-4d49-89e1-8e33cac31e4b ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0HJH5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 20485408280_1 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd09/02/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn0HJH5X:rvrA00:cvnDellInc.:ct13:cvr20485408280_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: cups (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/1474633 Title: Generic Text-Only driver misnamed or wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1474633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1474633] Re: Generic Text-Only driver does nothing
** Summary changed: - Generic Text-Only driver misnamed or wrong + Generic Text-Only driver does nothing ** Description changed: - I believe that the Generic Text-Only printer driver is either - misnamed, or is not functioning correctly. + I believe that the Generic Text-Only printer driver is not functioning + correctly. - The Generic Text-Only driver seems to be sending a PDF file to the - printer. This is not what I expected. A driver that sends a PDF file - to the printer should have a name like Generic PDF Printer. A driver - named Generic Text-Only should be sending text to the printer. We can - quibble about how many control codes are included in text. + The Generic Text-Only driver does not seem to send anything to the + printer. A driver named Generic Text-Only should be sending text to + the printer. We can quibble about how many control codes are included + in text. - I think the goal for a Text-Only printer should be that printing + I think the goal for a Text-Only printer should be that printing a file from a text editor should send the same data to the printer as copying the text file directly to the printer device (cat f.txt /dev/usb/lp2). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: - + CurrentDesktop: Unity Date: Tue Jul 14 23:12:33 2015 InstallationDate: Installed on 2014-09-05 (313 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lpstat: - device for Brother-MFC-7820N: usb://Brother/MFC-7820N?serial=000C5J505362 - device for file-P1092i-on-usb: /tmp/file-P1092i-on-usb.prn - device for P1092i-on-usb: parallel:/dev/usb/lp2 - device for Parallel-Brother: usb://Brother/MFC-7820N?serial=000C5J505362 + device for Brother-MFC-7820N: usb://Brother/MFC-7820N?serial=000C5J505362 + device for file-P1092i-on-usb: /tmp/file-P1092i-on-usb.prn + device for P1092i-on-usb: parallel:/dev/usb/lp2 + device for Parallel-Brother: usb://Brother/MFC-7820N?serial=000C5J505362 MachineType: Dell Inc. Inspiron One 2330 Papersize: letter PpdFiles: - P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended) - Brother-MFC-7820N: Brother MFC-7820N Foomatic/Postscript - Parallel-Brother: Brother MFC-7820N Foomatic/Postscript - file-P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended) + P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended) + Brother-MFC-7820N: Brother MFC-7820N Foomatic/Postscript + Parallel-Brother: Brother MFC-7820N Foomatic/Postscript + file-P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=de488065-a683-4d49-89e1-8e33cac31e4b ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0HJH5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 20485408280_1 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd09/02/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn0HJH5X:rvrA00:cvnDellInc.:ct13:cvr20485408280_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1474633 Title: Generic Text-Only driver does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1474633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366264] Re: wrong EFI partition modified
The installed Ubuntu 14.04.1 is mounting /dev/sda1 as /boot/efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366264 Title: wrong EFI partition modified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1366264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366255] [NEW] reportbug instructions wrong
Public bug reported: Following the instructions in the Boot Troubleshooting Guide https://help.ubuntu.com/10.04/installation-guide/ia64/boot-troubleshooting.html to try to report a problem with an installation, I ran aptitude install installation-report reportbug, then reportbug installation-reports. The instructions should have mentioned that I would have to run apt-get install aptitude. Running reportbug installation-reports produces *** ERROR: Ubuntu BTS is currently unsupported. Please use ubuntu-bug (from the apport package) for reporting bugs in Ubuntu. You can report bugs to Debian by specifying 'bts debian' in your ~/.reportbugrc or by passing the -B debian option on the commandline (see reportbug(1)). ** Affects: installation-guide (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/1366255 Title: reportbug instructions wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1366255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366264] [NEW] wrong EFI partition modified
Public bug reported:
I installed Ubuntu to an external drive. I told the installation
to use the ESP partition on the external drive. I think the
installation erased the ESP partition on the external drive, and added
itself to the ESP partition on the internal drive, briefly supplanting
Windows as the controller of EFI booting from that drive.
My machine came with Windows 8. I installed Ubuntu 14.04.1 64-bit
to an external USB Western Digital My Book.
Before installing Ubuntu conventionally, I had experimented with
creating an ESP on the WD drive -- 2 GB FAT16 partition named vdos.
In the root of that partition I had directories named EFI and boot.
I had copied some version of grubx64.efi to
${vdos}/EFI/boot/bootx64.efi. It was at the point where if I booted and
broke into BIOS Setup/Boot Options, one of the UEFI BOOT options was the
WD drive. Choosing that option got me my grub menu.
I burned ubuntu-14.04.1-desktop-amd64.iso to a DVD. I booted the
DVD in EFI mode (I can't swear I had Secure Boot enabled). I installed
Ubuntu, selecting Something else.
During the partitioning phase, I made sure that the Install GRUB
to was set to /dev/sdb -- the external USB drive. I filled in
designated uses for the ESP partition and an existing swap partition. I
created a new partition for the installation itself. I do not believe
that I checked the Format Partition box for any partition other than
the new partition I created for the installation.
When the installation completed and I rebooted, I had a GRUB menu
with a few Ubuntu options, and an option for Windows Boot Manager. I
probably booted Ubuntu, if only because the timer ran out while I was
taking notes. When I rebooted and broke into BIOS, there was no Windows
Boot Manager option in the BIOS BOOT Options. I booted Windows by way
of GRUB. I shut down. I rebooted and broke into BIOS Setup/Boot
Options. It said UEFI, Secure boot ON. There was only one UEFI BOOT
option, this time labeled Windows Boot Manager.
(I don't remember when/if I toggled Secure boot. I think I had
it enabled when I booted the DVD. I think I would have left it enabled
up to this point.)
From my Live-USB I found that the ESP partition on the external
drive was blank: no name, no contents. fdisk still reported it as
having type EF. I didn't check the filesystem type.
The ESP partition on the internal drive always had a top level
directory EFI. EFI now has an ubuntu subdirectory containing
grub.cfg, grubx64.efi, MokManager.efi, and shimx64.efi. The grub.cfg
chains to /boot/grub/grub.cfg on the Ubuntu installation (the Ubuntu
installation is /dev/sdc6 when the thumb drive is plugged in).
Copying ${wesp}/EFI/ubuntu/grubx64.efi to
${vdos}/efi/boot/bootx64.efi and ${wesp}/EFI/ubuntu/grub.cfg to
${vdos}/efi/ubuntu/grub.cfg results in BIOS showing a second UEFI Boot
option.
I started Windows both from the UEFI Boot option, and using the
option in the GRUB menu, and I still have WD My Book as a BIOS UEFI Boot
option. This leads me to believe that it was not Windows that wiped out
the ESP partition on the external drive
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Fri Sep 5 23:55:54 2014
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed
boot=casper only-ubiquity quiet splash --
InstallationDate: Installed on 2014-09-05 (1 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
ProcEnviron:
LANGUAGE=en_US
TERM=xterm
PATH=(custom, no user)
LANG=en_US.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 trusty ubiquity-2.18.8
** Attachment added: partman
https://bugs.launchpad.net/bugs/1366264/+attachment/4196856/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366264
Title:
wrong EFI partition modified
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1366264/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366264] Re: wrong EFI partition modified
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1366264/+attachment/4196861/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366264 Title: wrong EFI partition modified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1366264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366267] [NEW] download during install from Live-CD
Public bug reported: I installed using a DVD burned from ubuntu-14.04.1-desktop- amd64.iso. There was a lot of downloading going on during the installation, in spite of my having NOT checked update during install. There should be a way to install just the system I've been using on the Live-CD, with no checking for updates, let alone downloading updates. Particularly annoying was when it seemed to be downloading every language pack there is, so it could pick one and delete the rest. Maybe I don't understand what a language pack is, or why it felt the need to download more than one -- maybe a different label on that phase would make me resent it less while I'm waiting four to seven minutes for it to download. ** Affects: ubiquity (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/1366267 Title: download during install from Live-CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1366267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
