/srv/irclogs.ubuntu.com/2007/09/12/#ubuntu-installer.txt

CIA-18ubiquity: evand * r2226 ubiquity/ (configure configure.ac): bump to 1.5.1512:30
evandbzr shelve is awesome!12:31
xivulonwhat's that?12:37
evandhttp://bazaar-vcs.org/BzrShelveExample12:37
xivulonhmm I see12:50
=== xivulon [n=ago@87-194-85-156.bethere.co.uk] has left #ubuntu-installer []
evandcjwatson: As it stands in code that's about to be checked in, it's not possible to have a back button in automatic mode as any page we move over will answer all its questions, so there's nothing to go back to.03:04
evandIs this acceptable, or would you prefer I made the code that checks for the seen flag backup aware?03:04
CIA-18ubiquity: evand * r2227 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py): * Fixed backup in the UI wrt the new page turning code.04:28
=== cr3 [n=cr3@bas5-montreal02-1096553788.dsl.bell.ca] has joined #ubuntu-installer
=== superm1 [n=superm1@ubuntu/member/superm1] has joined #ubuntu-installer
cjwatsonevand: I think that's OK by me09:51
cjwatsonbzr shelve does indeed rock09:51
=== superm1_ [n=superm1@12-216-45-174.client.mchsi.com] has joined #ubuntu-installer
=== xivulon [i=c2325681@gateway/web/cgi-irc/ircatwork.com/x-a7a7a94986cbbe6c] has joined #ubuntu-installer
tepsipakkihi, tried to netboot gutsy, but grub-installer failed due to missing fdisk/sfdisk12:09
tepsipakkialthough they are there12:10
cjwatsonI had another report of that ...12:10
tepsipakkioh12:11
cjwatsonit's weird12:11
tepsipakkiyep, bug 13804012:12
tepsipakkibut should fdisk/sfdisk be present on the busybox side?12:13
tepsipakkithey are in /target12:13
cjwatsonyes, fdisk-udeb should provide them12:17
cjwatsonI'm just syncing the code over from the old laptop12:17
cjwatsonoh12:18
cjwatsonlamont broke fdisk-udeb12:19
tepsipakkiheh12:19
cjwatsontepsipakki: can you look in /var/lib/dpkg/status for me in the running installer, and check if fdisk-udeb is installed?12:26
tepsipakkiyep, it is12:31
cjwatsonok, good12:31
cjwatsonI reassigned the bug to util-linux12:31
cjwatsonand prodded lamont about it on IRC12:31
tepsipakkiInstalled-Size: 1612:31
cjwatsonit has /usr and /usr/sbin, nothing else12:32
tepsipakkiright..12:32
=== pj_og [n=chatzill@p57B2AC47.dip0.t-ipconnect.de] has joined #ubuntu-installer
pj_ogHi! I installed the ubuntu-server, but the base system doesn't boot. I have no idea why. I can boot memtest86+, but trying one of the kernels results only in a "reset". What now? The installation itself went absolutely smooth no error or so. But then rebooting doesn't work. I even have no idea how to debug such a thing since there are no messages. Any ideas anybody?01:08
pj_ogor if this is not the correct channel for this question, where would it be?01:12
cjwatson#ubuntu-kernel is probably better if the server kernel isn't managing to boot01:13
cjwatsonsounds like the generic kernel used in the installer is working fine, but the server kernel used after boot isn't01:13
cjwatson(normally the two kernels are the same, but in the server install they aren't necessarily)01:14
pj_ogok. thank you.01:14
cjwatsonxivulon: if you already had a wubi entry in the grub4dos configuration, running wubi again adds another one01:31
cjwatsonxivulon: maybe it should make sure that there's just one01:32
xivuloncjwatson, I noticed that yesterday night, but it was too late for me to fix that. Also the menu name should be changed to "Ubuntu Linux" in the vista case.01:34
xivulonIf you complete the installation (disk images are created), that is not an issue (since you cannot just reinstall, you have to uninstall first)01:36
xivulonForcing to uninstall anytime is the quickest way to fix that01:38
cjwatsonyeah, I actually just removed the ubuntu folder :-)01:41
cjwatson(wasn't sure if uninstall would work)01:41
xivulonI cannot upload code, but it should be a one line fix: wubi/installer/installer.nsh -> remove the {if} block around InstallCompleted01:41
cjwatsonI found another bug in the automatic-ubiquity handling, which I'll fix after lunchh01:41
cjwatsonlunch01:41
cjwatsonunfortunately unionfs is too broken in gutsy at the moment for me to get any further01:41
xivulon ${IF} $InstallCompleted == true01:45
xivuloncjwatson, simpler fix for uninstallation: in pages/main.nsh remove the above if statement01:45
xivulonleave the stuff in between01:45
xivulonThat will force you to uninstall if a previous installation is detected even if it wasn't completed.01:47
pj_ogHi, I'm back. I did not resolve yet my boot problem, but now I think there might be an installer problem.01:48
pj_ogMaybe sbd is interested?01:49
cjwatsonpj_og: sure, but I'm about to go to lunch, so mention it and I'll get to it after I get back01:49
CIA-18ubiquity: cjwatson@chiark.greenend.org.uk * rcjwatson@chiark.greenend.org.uk-20070912114801-ec22h8ue8sy9tpdh ubiquity/debian/ (changelog rules ubiquity.postinst): * Start ubiquity init script at 29; don't bother stopping it.01:49
pj_ogok. I managed to boot the generic kernel with grub, I just copied it over from the install CD01:49
cjwatsonurgh bogus bzr configuration01:50
pj_ogit kind of worked, but then there was a root disk problem or so, probably since the initrd didn't match really01:50
pj_ogso I think there might be some check which the installer might want to do to ensure that the installed kernel actually will work.01:50
cjwatsonit already tries. be more specific01:51
pj_ogsbd on kernel said that the server kernel probably assumes i686. I have a pentium MMX. I'm not sure, but it might be not enough.01:51
cjwatsonoh, that's fixed in gutsy01:51
cjwatsonit requires 686 for the server kernel now01:52
pj_ogof course, it could be another difference between the kernels. but with generic at least I get some messages, it starts to run.01:52
cjwatsonbase-installer's checks were indeed incomplete for server in <=feisty01:52
pj_ogI'm using the installer CD for 7.04 server01:53
CIA-18ubiquity: cjwatson * r2228 ubiquity/debian/ (changelog rules ubiquity.postinst): * Start ubiquity init script at 29; don't bother stopping it.01:53
pj_ogI tried to locate the technical requirements for the server from the ubuntu.com webpage but didn't find it01:53
cjwatsonCIA> that's better01:53
cjwatsonright, no need to file a bug though since 7.10 will get that check right01:54
pj_ogok. fine. and for my problem, I think doing an install with the normal CD might work?01:54
cjwatsonyep01:54
pj_ogor rather the alternate CD?01:54
cjwatsonit doesn't have the server kernel on it so won't try to se it01:54
cjwatsonuse01:54
cjwatsonyes01:54
=== cjwatson -> lunch, really this time
pj_ogok. thank you!01:55
pj_oggood lunch :-)01:55
=== cr3 [n=cr3@modemcable178.77-70-69.static.videotron.ca] has joined #ubuntu-installer
xivuloncjwatson, I think that the double menu entry is due to the name change of Wubi, since the registry key also changed and the old one went undetected02:34
xivulonYou probably had the previous version (called Wubi installed) and then run the new version (called Ubuntu)02:36
xivulonIn normal circumstances if you run the installer multiple times you should only have a single menu entry02:37
xivulonI think that the double menu entry is due to the name change of Wubi, since the registry key also changed and the old one went undetected02:37
=== xivulon ctrl+v again
xivulonThe current behaviour is that if Wubi was installed but no disks where created, the installer is re-run without uninstaller first, so that you can for instance resume an interrupted download02:39
xivulonIf virtual disks have been created, you have to uninstall first before you can run the installer again02:40
xivulonI think it is fine as it is02:41
xivulonOn second thought, it might be a good idea to always run uninstall on re-install and (optionally) backup partially downloaded files so that users can recover interrupted downloads02:59
cjwatsonxivulon: no, they were both called "Wubi Ubuntu"03:49
cjwatsonidentical names visible in the menu03:49
xivuloncjwatson, the "Wubi Ubuntu" is harcoded in wubibcd.exe (which is something I need to change), I am talking about the executable itself03:52
cjwatsonah, didn't check that03:52
xivulonWubi-7.10-XYZ.exe vs Ubuntu-7.10-alpha.exe.03:52
cjwatsonright03:52
cjwatsonI'll check next time I reboot to Windows, thanks03:52
xivulonThe first one uses "Wubi" as registry key, the second one uses "Ubuntu"03:52
xivulonThe key should be under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\03:54
xivulonTo undo the menu entry in vista manually, you have to get the boot menu ID stored in the registry, then run03:57
xivulonbcedit.exe /delete $ID /f03:57
=== avoine [n=avoine@modemcable003.251-59-74.mc.videotron.ca] has left #ubuntu-installer []
cjwatsonok, thanks04:05
=== avoine [n=avoine@modemcable003.251-59-74.mc.videotron.ca] has joined #ubuntu-installer
=== xivulon [i=c2325681@gateway/web/cgi-irc/ircatwork.com/x-49c821d352879979] has joined #ubuntu-installer
=== jetsaredi1 [n=jgreenwa@pool-141-149-173-208.bos.east.verizon.net] has joined #ubuntu-installer
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-installer
pj_ogAfter my n-th installation i now get a GRUB Error 18. What now?08:41
superm1_cjwatson, evand, the ubiquity-frontend-mythbuntu text, is it available in rosetta already, or does someone have to manually push it up?09:39
evandmy understanding is that it has to be manually updated.09:40
superm1_well my files from ubiquity-frontend-mythbuntu.templates merged into the ubiquity source package's po files i believe09:41
superm1_so it will probably happen whenever ubiquity itself is added up there09:41
evandindeed09:41
superm1_well i'll double check make sure that all of my stuff is accurate than in the english variant09:42
pj_ogMy problems are solved. I have a working system now - after something like 10 installations with different methods and a lot of guesswork. :-/10:02
evandyikes, glad it's working for you now10:03
pj_ogWell, yes, after 2 days of installation. First it did install a kernel which doesn't work for the processor used for the installation, then it didn't tell about the BIOS HD limit (maybe it simply can't), but then when I tried to install with different partitions (to get the boot kernel to the beginning of the HD), it fucked up some installations (probably due to too small a partition or so,...10:18
pj_og...or for some other reasons). Well, it's fine now, anyway.10:18
pj_ogI'm not exactly happy now since it ate so much time, but on the other hand, I think I can move on now to get the content on the machine and put it back online. Ouff.10:21
pj_ogOther than these temporary problems, I'm really satisfied with (k)ubuntu. So thanks to any developers reading here, all those who make this project possible.10:26
bdmurrayevand: Is swap always formatted?10:57
evandbdmurray: I believe so10:57
evandI seem to recall it being dangerous not to10:57
evandcjwatson: can you confirm?10:58
bdmurrayThe prepare partitions screen does show the "Format?" checkbox as being checked though10:58
evandwhenever you return to IRC, that is10:58
evandbdmurray: I don't follow.  Are you saying that contradicts swap always being formatted?10:59
bdmurrayevand: I am saying that I did not check Format and it still tells me it is going to be formatted.10:59
evandoh, hrm.  File a bug, please.11:00
evandat any rate the UI should be consistent11:00
bdmurrayYeah.  The fact that I am using Tribe 5 isn't relevant?11:01
evandIt shouldn't be.  Partman hasn't been changed in the frontend following the tribe 5 release11:02
bdmurrayevand: it looks like bug 83166 - do you agree?11:06
evandah, indeed it does11:13
bdmurraycool, as a stop gap couldn't the format box always be checked for swap?11:20
evandbdmurray: indeed, though I'd like to discuss the options with cjwatson before resorting to that11:22
bdmurrayevand: okay, I'll leave it in your hands. :)11:23

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