twbWhy is lucid's running the same old syslinux as jaunty?10:01
twbI wanted to use the "isohybrid" feature that allows me to make an install image that's both a bootable ISO 9660 image and a bootable USB hard disk image, but this feature was introduced around 3.70 -- which even Debian Lenny has :-/10:02
cjwatsonbecause it was really hard work to merge and I didn't have time to take on the QA load10:04
cjwatsondue to gfxboot, our syslinux is heavily patched.  hopefully that delta should drop with the update, but it was going to be hard work to make sure of that10:05
twbYeah, #syslinux thought it was probably gfxboot's fault10:05
twbApparently gfxboot is becoming a proper module, so that issue should disappear10:06
twbI guess I'll just have to work around it until 12.0410:06
applejackhello, how would I go about installing 10.04 on a blue/white g3? the cmd64x driver doesn't seem to be included, and the ata-generic driver won't see the harddrive10:19
twbapplejack: Ubuntu doesn't support the POWER architecture.10:19
applejackhmm,... the cd boots tho10:20
twbI think there are some unofficial ports10:20
applejacklet me rephrase then,. how do I stop the livecd from loading the ata-generic module?10:20
twbYou could try playing games in "expert" mode by bouncing into a shell and setting up blacklists10:21
twbOr modifying the CD, of course.10:21
applejackyea,. well, apart from doing that10:21
twbIf that unit supports the so-called "target ata", just plugging it into a modern machine and doing the install that way would be easiest10:22
twb(Or simply ripping the disk out and putting it into a modern machine while you install to it.)10:22
applejackyea,. done that10:22
applejackbut yaboot is broken10:23
applejackit seems that _has _ to be installed on hte hardware10:23
twbShrug.  I haven't dealt with newworld hardware for years.10:23
twbIf it were me, I'd first try fixing yaboot's config10:23
cjwatsonata-generic shouldn't actually claim the device unless there's nothing better around to drive it10:25
cjwatson(unless you boot with all_generic_ide)10:25
applejackcjwatson: that's the problem,... the cmd64x driver is not on the livecd, so there is nothing better10:25
applejackand it's needed for the cd I suppose10:26
cjwatsonright.  please file a bug on the Ubuntu kernel asking them to turn on cmd64x for powerpc, so that at least this gets fixed in the future10:26
cjwatsonit's simply not built for powerpc at all, as far as I can see, it's not just that it isn't on the live CD10:26
cjwatsonwhich makes a workaround kind of hard10:26
cjwatsonit'd make it a customisation job - or you could plead with the kernel guys to get this into a stable update for lucid, so that we can include it in a point release or something10:27
evmichaelforrest2: ready?11:04
michaelforrest2ev: yep - wanna come in here?11:09
michaelforrest2(TV ROOM)11:09
twbOK, WTF.  I just went through a netboot install of lucid, doing my usual partman configuration of /boot ext2 on RAID1 on sd[ab]0 and root ext4 on LVM on RAID1 on sd[ab]1.12:46
twbWhen I go to boot the system, I find that /boot won't assemble, /dev/sd[ab] themselves are md1, and /cat/proc/partitions is reporting partitions sd[ab]{,0,1} and md1{,p1,p2}12:47
twbI could do without this kind of surprise at 10PM on a Friday :-/12:48
applejacksd[ab]0 ?!??12:49
twbEr, sorry, off-by-one error12:50
twbLemme transcribe it exactly12:50
applejackdoes it assemble if you do it manually?12:51
twbmdadm -A /dev/md0 --scan ?12:52
twbI'm also a bit grumpy about plymouth being installed on a server when the only thing I picked in tasksel was libvirt.12:52
twbThe entries in /proc/partitions are sd[ab], md1, sd[ab][12], md1p[12], and the LVM LVs.12:53
twbmdadm -A /dev/md0 --scan causes it to assemble md0 with one drive -- md1p112:54
applejackmdadm --examine --scan ?12:55
twbI'm guessing somehow nobody bothered to test the new partitions-on-md-devices code in this particular configuration.12:56
applejackyou need to make your root md device NOT use the first 512 byte of the drive12:58
applejackI forget the option to create it that way12:58
cjwatson--zero-superblock might be relevant12:59
twbWell, I didn't make it use the first 512 bytes12:59
twbThat's where the MBR should be12:59
cjwatsonplymouth is mandatory for all Ubuntu installs, and it's not just for splash screens, I'm not going to go into that discussion yet again12:59
twbI mean: I just asked partman to lay out normal partitions.12:59
sorentwb: plymouth is in ubuntu-minimal. It's got nothing to do with libvirt.13:00
sorentwb: Oh, cjwatson just pointed that out. Never mind.13:00
twbsda was previously a SCO 5 disk; sdb was almost certainly blank.  I *think* I told partman to make a new disk label, but I might misremember.13:00
twbIt appears that openssh-server is installed, but not running.13:02
twbAh, it'll be because I dropped into a recovery shell when /boot failed to mount, so I never reached the "filesystems" event that ssh.conf was waiting for.13:03
twbIncidentally, when using qemu -curses, is there an -append option I can add to prevent lucid from loading vga16fb?  qemu -curses can render the 80x25 VGA console, but not framebuffers.13:09
twb(Contrariwise, I can happily report that everything Just Worked when I installed lucid on a headless/serial-only Soekris net5501 router recently.)13:11
twbhttp://pastebin.com/DrhNVj7Q is the output from the current md1p1-wacky host13:14
cjwatsonblacklist=vga16fb should do it13:22
twbI was trying all sorts of things like video=false and vga=normal to no avail13:22
cjwatsonthose ought to blacklist vga16fb too13:22
cjwatsonwhich implies blacklist=vga16fb mightn't help, but you can try it ...13:23
twbI will when I roll my next VM13:23
sorenIt works for me, fwiw.13:27
sorenAll of those do, actually.13:28
sorenvideo=false, vga=normal, and blacklist=vga16fb.13:28
twbsoren: in qemu?  What version of qemu?13:28
sorenWhatever's in Lucid.13:28
cjwatsonI suspect that something after the initramfs is loading vga16fb13:28
sorencjwatson: Ah, point.13:28
sorenI only tested up to and including initramfs.13:29
cjwatsonthe handling for those options is specific to the initramfs13:29
cjwatsonI don't know what, though13:29
twbI vaguely remember looking at the module config shortly before lucid was released13:29
twbIIRC it said something like "make sure we never ever load a non-KMS fb" followed immediately by "except we should always always load vga16fb"13:29
sorentwb: With blacklist=vga16fb, I can boot all the way to a login prompt with -curses.13:33
soren(in maverick, at least)13:33
twbOK, I just reproduced it in the netboot kernel before I get as far as installation.13:38
twbqemu-system-x86_64 -curses -kernel linux -initrd initrd.gz -append 'blacklist=vga16fb fb=false video=false vga=normal'13:38
twbUsing qemu0.11.1-2.ubuntu1 and mirror.internode.on.net/pub/ubuntu/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/{linux,initrd.gz}13:39
twbI'll grab the archive.ubuntu.com kernel and ramdisk to be doubly sure13:40
twbYeah, same cksums for archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/{linux,initrd.gz}13:42
soren...and that doesn't work for you?13:44
twbIt gets as far as [    4.676325] fb0: VGA16 VGA frame buffer device13:45
twbThen I get "640 x 480 Graphic mode" from qemu, and can't see anything13:45
twb(Actually there are a couple of messages about e.g. virtio shortly after that kmsg, but I didn't capture them.)13:46
sorentwb: Ah, that's the installer initrd. It might be different that what's in an installed system.13:46
sorenWell, it /is/ different, of course, but in a way that matters for this use case.13:46
twbI don't really care about an installed system because 1) it'll be pre-seeded to include openssh-server; and 2) I can do arbitrarily filthy things, "install vga16fb true" in /etc/modprobe.d/kludges.conf13:47
twbBut in the initrd, it means I *must* preseed at least enough to get the sshd udeb installed, or use -nographic (serial) or -vnc :0.13:48
twbsoren: I *can* confirm that blacklist=vga16fb DTRT in a lucid live CD generated by live-helper.13:56
CIA-4grub-installer: cjwatson * r855 ubuntu/ (debian/changelog grub-installer): Install grub-efi on i386/efi and amd64/efi subarchitectures.15:20
CIA-4partman-basicfilesystems: cjwatson * r587 ubuntu/ (debian/changelog fstab.d/basic): Automatically mount the first method=efi filesystem we see on /boot/efi.15:37
CIA-4partman-basicfilesystems: cjwatson * r588 ubuntu/debian/changelog: releasing version 63ubuntu615:39
CIA-4partman-auto: cjwatson * r323 ubuntu/ (9 files in 3 dirs):15:41
CIA-4partman-auto: Add i386/efi (and amd64/efi, kfreebsd-i386/efi, and kfreebsd-amd64/efi)15:41
CIA-4partman-auto: recipes that create an EFI System Partition.15:41
CIA-4partman-auto: cjwatson * r324 ubuntu/debian/changelog: releasing version 91ubuntu215:42
cjwatsonev: do you know how the foundations-m-gsoc-usbcreator-* work items for alpha-2 are going?15:46
evcjwatson: I've moved them to A3.  I don't think they'll be ready for A2.15:59
cjwatsonok, thanks16:04
evmichaelforrest: the plan is to get rid of the hostname box entirely, correct?17:21
twbFYI, the Australia/Melbourne vs. Australia/Victoria timezone detector thing is working now.18:01
twbLooks like I can't remove the sda5_crypt that guided partition created via partman -- but I *can* just spawn a shell and run "cryptsetup remove sda5_crypt".18:21

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!