[Bug 423616] Re: casper boot doesn't work with some boot options
Launchpad Bug Tracker
423616 at bugs.launchpad.net
Tue Oct 2 22:29:11 UTC 2012
This bug was fixed in the package casper - 1.326
---------------
casper (1.326) quantal; urgency=low
* 22desktop_settings:
- Rename 22screensaver to 22desktop_settings
- Move 22gnome_panel_data's content to 22desktop_settings
- Flush overrides in 22desktop_settings to avoid getting duplicate keys
when using persistence.
- Check for gsettings-desktop-schemas instead of gnome-panel-data
* 35fix_language_selector:
- Use sed against the original file (from rofs) instead of the target file.
This avoids another case where the change is re-applied at every boot
when using persistence.
* 25adduser:
- Remove RUNNING_UNDER_GDM from /etc/environment which was a big hack
for back when we still used xscreensaver and was getting appended with
every single boot.
- Use /etc/sudoers.d instead of appending to /etc/sudoers, avoid getting
duplicate lines with every reboot.
* 23networking:
- Change default /etc/network/interfaces to match that in /rofs, makes it
easier to diff /etc when debugging casper.
* casper-init, casper, 19-keyboard, casper-functions:
- Remove any remaining reference to usplash as it's been deprecated for a
long long time and just makes things harder to read.
* casper-update-initramfs:
- Exit when called from a non-writable media (cdrom) or when called from
ubiquity. This fixes a > 1 minute wait when clicking "Try Ubuntu".
* 19keyboard:
- Add code to detect that the keyboard layout changed from the previous
value and flush the gsettings key so that the indicator is properly
reset. (LP: #946406)
* 43disable_updateinitramfs:
- Don't try to chmod a dangling symlink.
- Only write /usr/sbin/update-initramfs if it doesn't already exist.
* postinst:
- Remove code generating symlink for /usr/sbin/update-initramfs to
/usr/share/casper/casper-update-iniramfs as the diversion and symlinking
is done in the initramfs and that code was only useful when the shim was
first introduced. (LP: #984276)
* scripts/casper:
- Allow specifying live-media on the command line, helps when booting
computers that are unable to boot a CD/USB disk. (LP: #423616)
- Fix NFSOPTS handling by adding the needed comma and sticking it to the
existing "ro" option of nfsmount (LP: #476208)
* 22serialtty:
- Move 22serialtty to 26serialtty to avoid overriding the newly generated
upstart jobs. Note that this will spawn getty instead of login, but
it's probably for the best as we need a specific baudrate. (LP: #747888)
-- Stephane Graber <stgraber at ubuntu.com> Tue, 02 Oct 2012 18:11:44 -0400
** Changed in: casper (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/423616
Title:
casper boot doesn't work with some boot options
Status in “casper” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: casper
I'm booting a system on a USB key from an old laptop having no bios option to boot from usb, nor bios recognition of usb at boot.
This is useful to install new ubuntu distros without burning CDs even on old and very old machines, avoiding producing trash.
The usb keys are obtained by ubuntu usb live creation on FAT32 usb keys (Karmic and Jaunty).
The method used is to boot a kernel and ram image previously copied on hard disk from USB in /boot/usb-boot directory, but using as root the usb key.
In any case I wasn't able to open the system as the live cd, asking
for language and keyboard - I was only able to boot the system this
way :
title Xubuntu from USB
uuid 26d5b9d3-5e38-400f-906c-ea685407c590 #uuid of hard disk
kernel /boot/usb-boot/vmlinuz floppy.allowed_drive_mask=0 root=UUID=46F1-C9E3 boot=casper noprompt cdrom-detect/try-usb=true lang=it locale=it_IT
initrd /boot/usb-boot/initrd.gz
boot
where : 46F1-C9E3 is the uuid of the usb key.
floppy.allowed_drive_mask=0 is an option needed both in Karmic and Jaunty to avoid booting to stop looking for fd0 (I/O Error on fd0) - BTW - with this option the system works but complains as "Unknown option" - if option is absent, system doesn't work; I also tryed to grub-install with --no-floppy option but no effect.
The system work when only the previous option are included, but both
in Jaunty and Karmic, those options do not work :
1) keyboard=it or keyb=it or xkeyboard=it (no effect)
2) bootkbd=it (system doesn't boot, and this is the standard option from https://help.ubuntu.com/community/BootOptions)
3) console-setup/layoutcode=it (system doesn't boot)
4) file=/cdrom/preseed/xubuntu.seed persistent (system doesn't boot)
When system doesn't boot, it looklikes looking for a media it can't
read (/dev/sdb, /dev/sr0......), and we get a loop.
Do I need to copy extra files in /boot/usb-boot?
5) option bootkbd=it in syslinux.cfg let system booting, but no effects;
6) manual change allows to set keyboard (Applications/Settings/Keyboard) and setxkbmap it works too
For my use, the "persistent" option is not indispensable; A boot with
the right keyboard would be preferable for multiple installs;
7) option xforcevesa doesn't work (no boot) option vesa has no effect
Thx
Paolo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/423616/+subscriptions
More information about the foundations-bugs
mailing list