/srv/irclogs.ubuntu.com/2010/06/23/#ubuntu-installer.txt

Joithi where can i make a suggestion about the install from the live cd / blackscreen11:18
cjwatsonstop asking where, and just spit it out :-)11:18
Joit :p11:19
Joiti add at the recover mode at the linux line nomodeset, and it fixed it, to go through all screens11:19
Joitjust, as is pick from the menu dpkg it removed the line again, and i had to put it new in, but then i came to kde, and i could install nvidia driver from the net11:20
Joitand beside, it fixed some broken pckage, what seems are at the cd11:20
cjwatsonum, is this a maverick daily build?11:20
cjwatsonreleased images shouldn't have any broken packages11:20
Joitno, ubuntu 10.411:21
cjwatsonthen there is some deeper problem, and you should just file a bug with full logs and explain exactly what you were doing11:21
Joitwell i did dload it couple times, but few files still had allways an error11:21
cjwatsondid you check the image checksums, and have you cleaned your CD drive?11:21
Joitat last it worked, to install it over the live cd11:21
Joitwell i burned it with 3 different burners, but its allwas the sae file11:22
cjwatsondid you check the image checksums?11:22
Joitand did dload the iso few times also11:22
cjwatsonwe don't release images with broken files, ever11:22
Joiti did not check them really, no11:22
cjwatsonwhat exactly is the error message?11:22
cjwatsonthe one that leads you to believe that there are broken packages on the CD11:22
Joitwhen i check the cd for errors it says can not be readed11:23
cjwatsonwhat exactly is the error message?11:23
cjwatsonplease don't paraphrase it :)11:23
Joitwell, what you expect from my grey cells :p11:23
Joiti will check it, and put the cd in on the other pc11:24
cjwatsonif I see the exact error message, copied exactly, then I can probably say whether it's a physical hardware problem or a software problem11:25
Joitmm wait, that was after install11:25
Joiti did install it with the live cd11:25
Joitafter it was installed, i figured it out, how to boot with nomodeset, and get he screen with this optinos for continue normal boot dpkg check and few others11:26
Joiti did run dpkg and it gaves me this message, looking for broken pakages11:26
Joitand it did start dloading 170 mb11:27
cjwatsonEXACT11:27
Joitbut i have no log for that11:27
cjwatsonsorry to shout but you keep paraphrasing things11:27
Joitlol11:27
cjwatsonI just want a copy of the error message you're seeing11:27
cjwatsonseriously, it's so much quicker11:27
cjwatsonhttp://www.chiark.greenend.org.uk/~sgtatham/bugs.html11:28
cjwatsonif you have to go through recovery mode after installation, then something has gone wrong during installation and it would be easier to just fix that11:28
cjwatsonso, I need the full installation log to find out what11:28
cjwatsonyou should find it in /var/log/installer/syslog11:28
Joiti think more, that it did not have the right driver for the nvidia, its from 6xx serie11:29
Joitbut my point is actually not the broken packages, but for the recover mode the parameter nomodeset would be better11:30
cjwatsonI don't think that's true across the board, sadly11:34
cjwatsonit will make some hardware work better and other hardware work much worse11:35
cjwatsonit's not something we can apply everywhere - if it were then it could just be the default11:35
cjwatsonit's awkward11:35
Joitbut for the first install it is soemthing neutral isnt it11:35
cjwatsonI would not say so11:35
cjwatsonwe're getting to the point where modesetting is in general much better tested and much more reliable, with a few exceptions such as the one you appear to be running into11:36
Joitbut anyhow it bothers me, that actually most cards has a vesa mode, what is there since begiinning, and the most should work with it11:36
cjwatsonand I think the tradeoff now is that people with your kinds of problems should be reporting bugs to get modesetting fixed, rather than campaigning to have modesetting switched off in some situations11:37
cjwatsonnomodeset is there as an emergency escape hatch for people with problems, but it isn't a permanent situations11:37
cjwatsonsituation11:37
cjwatsonerr.  I mean "solution"11:37
Joitwell grub gives a hard time also to keep it in, i tried to add the line, but it seems he did ignore it11:38
Joitjust worked with a wooden mallet11:38
Joitok finnished now, i did pick the option check cd for errors, it ended and only pop up errors found in 13 files11:39
Joitthis was the live kbuntu cd11:39
Joit10.411:39
Joitpress any key to reboot...11:40
cjwatsonwhat errors?11:40
Joitit did not say more then this line11:40
cjwatsoncan I have the installation log, please?11:40
Joitthat is what i got when i boot from the live cd, and choose check cd/dvd11:41
Joitdoes it save it that way?11:41
cjwatsonah, no11:42
cjwatsonso if that shows errors, it's really not worth attempting an installation11:42
cjwatsonwe'd force everyone through that check by default except that it's sloww11:42
cjwatsonyou need to figure out why the check fails - the one thing I can say is that it's certainly not a problem with the master ISO image; even if it had got through QA like that, we'd have heard more about it by more11:43
cjwatsonby now11:43
cjwatsonso either you have a network problem that means that the download persistently gets corrupted for you, or you have a bad burner, or the reader in the computer you're trying to use is bad, or the actual disk is broken somehow, or (rarely) there's a bug in the kernel that means it fails to read from your CD controller11:44
Joiti dont know, really, i did dload the iso's few times from different mirrors, did burn them with different burner, but allwas get a error at some certain files.11:44
cjwatsonI understand, but that is where the problem lies11:45
Joitwhen this would happen at normal copying files at my pc, i would say, the source is bad11:45
Joitbtw, i checked the syslog, it is emtpy11:45
Joitat last kubuntu runs now by me, after i did get the right drivers from the net and it fixed the files over dpkg11:46
Joitand back to grub, seems vers2 is not really better at adding lines during the boot11:46
Joitanyhow, it seems it cant keep it right now11:47
cjwatsonjust add them to the right lines in /etc/default/grub and run update-grub11:47
cjwatsonthere's a big comment at the top of /boot/grub/grub.cfg telling you what to do11:47
Joitwell, when i have the problem with the blackscreen , i cant add anything, becuase i dont have access to this files11:48
ograon a sidenote there are MD5SUM files on the download server, did you check your iso against them ?11:48
Joitno i did not, md5sum is a terminal prog, and i tried first to dload the files freh, or burn them11:49
ograwell, that should be the first checkpoint if the selftest fails11:51
ograchecking the iso is ok11:51
ograif that is the case, its likely that your media is broken or you burned to fast, burning at slower speed might help11:52
Joitwell, when i dload a iso, i think, they should been checked from the one, wo upload them11:52
ograthey are11:52
Joiti did burn them also slowly, 8x, and with infrarecorder, thats a program, what they suggest at the ubuntu page11:53
ograwhich is why the md5sum files are provided, but that doesnt help if your iso gets corrupted on download11:53
cjwatsonadding kernel arguments during boot should be straightforward - they go on the end of the 'linux' line11:53
cjwatsonyou can 'cat /proc/cmdline' after boot to check that they took11:53
Joitwell i use a free download manager, and i never get a corrpted file with it11:54
Joitso it guess it must be the source11:54
cjwatsonthe source is correct11:54
cjwatsonhonestly, I understand why you're saying this, but we would know :-)11:54
Joitand few different sources, burned with different burners, allways the same file what is corrumpted, what would be there logical?11:55
Joiti will see, what i can do with md5sum11:55
ograright, start with that11:55
Joitwell, actually nm, i have it installed, and now knopw, how i can do it again, if, and therefor i dont bother much more with it11:56
cjwatsonby way of showing good faith, I'm re-checking the Kubuntu 10.04 desktop image now11:57
Joitand this blackscreen issue is often at this Version, its not only me11:57
Joitty i appreceatie it :P then i dont feel alone11:57
cjwatsonit checks out with zero errors here11:57
cjwatson(under emulation, which is why it was quick)11:57
cjwatsonso the ISO image on releases.ubuntu.com is definitely fine11:57
ogracjwatson, btw, looking at the ton of bugs we get from mis-edited /etc/default/grub files i was wondering if grub shouldnt ship something like visudo at some point :)12:01
ogra"vigrub" :)12:01
Joitok the checksum for ubuntu-10.04-desktop-i386.iso do match12:03
ograprobably a worthy spec for M+112:03
Joitthe file is right on my pc12:03
Joitand it seems more like, there are bad files on the cd, and the checksum is made with them12:03
Joiti doubt, that my burner produce the error12:04
ograwell, its either your media or the burning that breaks them12:04
Joitor, my 3 burner12:04
Joitwell 3 different burner, allways the same file ? that is ridicoulus, sorry12:04
ograwell, cjwatson just checked the iso again above ... the content of the iso is ok, your md5sum matches the one on the server so the only way it can break is while transferring it to or from the media12:05
Joitcjwatson where did you get yours from12:06
Joitand well, another idea, that we have differnt hardware, and the errors are at the files for my exotic12:06
ograunlikely that will affect an md5sum check on the disk12:07
ograunless your CD reader is bad or something12:07
Joiteven when it is not really exotic, its a hp t3000 with an asus a8zmn-la board with nvidia on board12:07
cjwatsonJoit: http://releases.ubuntu.com/kubuntu/10.04/kubuntu-10.04-desktop-i386.iso12:08
cjwatsonthat is the canonical, official copy12:09
cjwatsonits md5sum is 0ef722fd6b348e9dcf03812d071d68ba, matching the one on the central build machine (which I have access to, since I co-administer it)12:10
Joitat last, i could try to burn the iso as iso on a cd, and do there the md5check again12:10
Joithm mine is different12:10
cjwatsonwait, you said Ubuntu 10.04?  is it Ubuntu or Kubuntu?12:11
cjwatsonsorry then, you confused me by mentioning KDE above12:11
Joitits the one from from ubuntu12:11
ograyou said kubuntu initially12:12
Joitd044a2a0c8103fc3e5b7e18b0f7de1c812:12
Joit ubuntu-10.04-desktop-i386.iso12:12
ogra<Joit> this was the live kbuntu cd12:12
ogra<Joit> 10.412:12
Joithttps://help.ubuntu.com/community/UbuntuHashes12:12
cjwatsond044a2a0c8103fc3e5b7e18b0f7de1c8 is correct12:12
ograhmm, no you said kbuntu :)12:12
Joityes, and that is what i got12:12
cjwatsontherefore, it is not a download problem12:12
Joityes, that is, what i did install12:13
Joitbut i did now the check with the ubuntu cd12:13
cjwatsonall files on that image check out correctly here12:13
cjwatsonit is not a problem with the source image12:13
Joiti think not the image is the problem, but the config files there12:13
cjwatsonyou are wrong12:13
cjwatsonI'm sorry but it is as simple as that12:13
cjwatsonwe've spent lots of time going over this and ruling that out12:14
cjwatsonso please let's not waste any more time on that12:14
cjwatsonthe problem is either (a) burner (though you seem to have mostly ruled that out) (b) reader (c) kernel12:14
Joitwell, as i said, my point was about the blackscreens, this broken files was at last more an sie effect12:14
cjwatsonoh or (d) media12:14
* ogra votes for d12:15
cjwatsonit's not worth investigating problems with a broken installation CD12:15
Joitcjwatson well you did not proof me, that my burner mess it up12:15
ograhe did12:15
cjwatsonJoit: no, and I didn't intend to - there are still multiple possibilities12:15
cjwatsonogra: please don't put words into my mouth12:15
ograwell, you did proof its neither the download nor the iso that breaks it12:15
cjwatsonthat does not prove that it is the burner's fault12:16
ograright, sorry12:16
Joitwhat is so hard to get there, i put the cd in, it shows the install menu, and after enter, to install, the screen goes out of range12:16
cjwatsonI was quite clear about that just above12:16
Joitand when i put the param nomodeset in, it works12:16
cjwatsonJoit: the first step should be to make sure that the CD is being read correctly; practically any imaginable problem could result from failures there12:16
Joitogra i did do nothing, its how you will understand it, thats the point12:16
cjwatsonJoit: but, once that is fixed, the problem is not one of configuration, but the fact that the kernel does not work out of the box12:17
cjwatsonthe Ubuntu kernel should not *require* special configuration options to work out of the box12:17
cjwatsonit is unambiguously a kernel bug if it does12:17
Joitwell anyhow is something messed there, and its not my burner or my cd12:17
cjwatsonso we won't add nomodeset to recovery mode by default, but I encourage you to file a kernel bug about the fact that it doesn't work out of the box12:18
cjwatsononce you've sorted out the CD problems, anyway12:18
Joitand i am pretty sure about that, i did play now 2 days with that around, and dont see a other solution12:18
Joitno, i am certain, that i burned min 2 correct.12:18
Joitbut i still get errors in the files12:19
cjwatsonthe one thing I have proven is that there is no such checksums error in the ISO image12:19
Joitthe checksums are made, after the files been added12:19
Joitit is no guarantie, that there are not bad files into the pakcage12:20
cjwatsonthe check that you performed checks the checksums12:20
cjwatsonso that's not relevant12:20
Joitwell anyway, its maybe right, that the param not will work at all boards, but i could not add it at grub after installtion12:21
cjwatsonwhere did you try to add it?12:21
Joitwhen i add it with the live cd, it works, but not with grub, After the load screen 'e' and then to the line where it loads the kernel12:22
Joitafter quiet splash12:22
cjwatsonand what did you press after that?12:22
Joitesc12:22
cjwatsonthat cancels your modifications12:22
Joitok, then thenormal way would be ctrl+c after taht to get a prompt and type boot?12:23
cjwatsonhere's the message it shows below the menu12:23
cjwatson"Minimum Emacs-like screen editing is supported. TAB lists completions. Press Ctrl-x to boot, Ctrl-c for a command-line or ESC to discard edits and return to the GRUB menu."12:23
cjwatsonso make your modifications, and then press ctrl-x12:23
cjwatsonyou don't need to use the command-line via ctrl-c12:23
Joita little secrect more, what they hiding, it is not described at the grub page12:24
cjwatsonit's displayed right there on the screen you got with 'e'12:24
Joitat this screen after e are only the command lines in a box12:25
cjwatsontake a photograph and show me?12:25
Joitlo12:25
Joitl12:25
Joitand send you a postcard also ? even when i would12:25
Joitok it says... in german12:26
cjwatsonoh, damnit, I bet this is bug 58017812:27
ubot2Launchpad bug 580178 in grub2 (Ubuntu) "German translation of editing screen legend considered harmful! (affects: 2) (heat: 93)" [Undecided,New] https://launchpad.net/bugs/58017812:27
cjwatsondamn fool translators12:27
Joitminimal emacs similar screen processing is supported.  tab for aautocomplete press STRG-c for prompt or esc for back to the menu12:27
Joitno ctrl x12:27
cjwatsonright, the German translation is broken12:27
Joitstrg=ctrl12:27
cjwatsonit's ok, I understand German12:27
cjwatsonwell enough for that anyway12:27
Joitdarn, why allways that12:28
cjwatsonin that case I apologise, it wasn't your fault but your countrymen's ;-)12:28
cjwatsonbut it is specific to German, it's displayed in other languages12:28
cjwatsonI'll see if I can at least get that bogus translation disabled12:28
Joit,, i suppose the bug is in progress to get fixed12:29
cjwatsonit wasn't, but it can be, at least disabling it and showing the English text instead12:29
cjwatsonbetter correct English than wrong German12:29
cjwatsonanyway, press Ctrl-x after making your changes12:29
Joitwell, mainly i still think more at this blackscreen issue.. but since it seems is not a solution, or can mess at some boards up..12:30
Joiteven when i thought, it can be at recover mode, because there should be save settings12:30
Joitor something, where you set a vga modus12:31
Joitsave* vga modus12:31
dpmJoit, I caught the conversation and I saw the bug. What does the message exactly says in German? I do see Strg+X mentioned in the translated message at https://translations.edge.launchpad.net/ubuntu/lucid/+source/grub2/+pots/grub/de/205/+translate so there might be something else going on12:33
cjwatsondpm: it looks like it was fixed after the lucid release12:33
cjwatsonor after the last language pack pull, anyway12:34
cjwatsonalthough the packaged translation in lucid is wrong; it's fixed in maverick12:34
cjwatsonthe msgstr in language-pack-de-base/lucid-updates is:12:34
cjwatson"Minimale Emacs-ähnliche Bildschirmbearbeitung wird unterstützt. TAB listet "12:34
cjwatson"Vervollständigungen auf. Drücken Sie Strg-C für eine Befehlszeile oder ESC, "12:34
cjwatson"um zum Menü zurückzukehren."12:34
JoitPackaged:    12:35
JoitM12:35
Joitit is that mesasgw, what is under packages12:35
ogra"TAB listet Vervollständigungen auf" thats a weird description of what it does12:35
Joitand the same, what cjwatson pasted, just dont have all letters there :p12:35
cjwatsonI should be able to get a fix for that string into 10.04.112:36
Joityes tab did not work actually, it only switched to the / and showed the dir s there12:36
Joitmd5sum12:38
ogra"TAB vervollständigt Eingaben" would be the proper description12:38
Joitsry wrong window12:38
dpmcjwatson, I see, the Packaged translation in LP mentioning Strg+X confused me as well. So there must been a post-release update to grub which imported new packaged translations, and possibly a fix to the Ubuntu translations post-release which did not make it to the latest language packs. In any case, rather than showing the English string for the fix, we could update the language packs or pull that translation12:40
cjwatsonthere was a post-release update to grub, but it did not change translations12:40
cjwatsonhowever that doesn't rule out LP having done something strange to it12:41
cjwatsonwe can update the language packs for .1 (we should anyway) and update the incorrect packaged translations12:41
cjwatson*translation12:41
cjwatsonthat will cover all the bases12:41
dpmyep, that sounds like a good plan12:41
dpmI'm still confused to what happened here, though, I'll see if the LP devs can cast some light on this later on12:42
Joitwell i checked now kubuntu desktop iso, and it is right at my pc too12:47
Joitthe checksum is12:47
Joitalso someone else at #ubuntu said, he could install it normally12:48
Joitso either it is my hardware, what is not supported or the specific driver for this kind is broken12:49
Joitand sorry, i still doubt, that my burner did mess it :p12:49
cjwatsonI didn't say that your burner messed it up.  I raised that as one of several remaining possibilities.12:50
cjwatsonbut I'm getting a bit tired of re-explaining myself, I'm afraid12:50
Joityes, and i know, that it is a very close possibility12:50
Joitwell, i understand at the other side too, each supermarket drops each months a new pc out, where they trow all the chip hardware in, and not sure, how they can mix it all together allways12:51
Joitto find a solution for all of them is maybe a bit hard12:51
Joitcheap hardware, i meant12:52
Joitand i remeber other pc's where it did look like, they had a lock in it, that you only can install her Cds and OS on it12:53
TheMusocjwatson: Is there any documentation for ubiquity's plugin API anywhere? I haven't really looked yet, but couldn't find anything obvious in the ubiquity source.12:59
Joitdarn now i see, i did dload the wrong edition, this one maybe would be better http://ubuntusatanic.org/screenshots.php13:02
cjwatsonTheMuso: https://wiki.ubuntu.com/Ubiquity/Plugins13:02
TheMusocjwatson: thanks muchly.13:03
Joitok, i need to go, gday and have fun, and thanks for listen13:04
=== ara_ is now known as ara
=== ara is now known as Guest95569
=== Guest95569 is now known as ara
=== JanC_ is now known as JanC

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