=== yokgibi [n=yokgibi@88.245.84.98]  has joined #ubuntu-installer
[12:56] <yokgibi> hi all
[12:56] <yokgibi> may i ask some question
[12:56] <yokgibi> ?
=== superm1 [n=superm1@ubuntu/member/superm1]  has joined #ubuntu-installer
[12:58] <yokgibi> please ...
[12:59] <superm1> yokgibi, did you have a question?
[01:00] <yokgibi> yes
[01:00] <yokgibi> i had a trouble with feisty installation
[01:00] <yokgibi> when i trying the install
[01:01] <yokgibi> installer ask username-password
[01:01] <superm1> Right
[01:01] <yokgibi> in forums, people said may be 'ubuntu'
[01:01] <yokgibi> but i try it and the others
[01:01] <yokgibi> re-download iso
[01:01] <yokgibi> then retry, no result
[01:02] <yokgibi> may you help me ?
[01:02] <yokgibi> sorry for bad english
[01:03] <superm1> well you haven't said your question yet :)
[01:04] <superm1> you make it to the installer username/password and what happened?
[01:04] <btm> I think he is getting a login prompt at some point and doesn't understand what to enter.
[01:04] <yokgibi> yes
[01:05] <yokgibi> before, i install feisty succesfully
[01:06] <yokgibi> but now, when i try install, like btm said, a prompt seen
[01:06] <yokgibi> and i don't know about username/password
[01:09] <superm1> well those are normal questions
[01:09] <yokgibi> result ?
[01:09] <superm1> you choose a username and password to use for the install
[01:09] <yokgibi> how ?
[01:10] <yokgibi> i burn iso to cd directly
[01:10] <yokgibi> how i choose in this process
[01:10] <yokgibi> how i choose username/password in this process
[01:11] <superm1> well what'ever you would like to use
[01:11] <superm1> they are just for personalizing the install
[01:12] <yokgibi> i want to be personalize ubuntu, not ubuntu installation
[01:13] <yokgibi> whatever, so how i set username / password for installation
[01:15] <superm1> in the installer it asks you for both, you just type them in and hit "next"
[01:15] <yokgibi> :)
[01:16] <yokgibi> it ask username / password before starting install script
[01:16] <yokgibi> before boot livecd
[01:16] <superm1> before booting?  Then that is somethign in your client os
[01:17] <yokgibi> boot from cd, choose 'Start or Install Ubuntu', wait sometime and login prompt :)
[01:17] <superm1> okay that's making more sense here with your issue then -
[01:17] <superm1> try to choose safe graphics mode
[01:17] <yokgibi> i tried
[01:18] <yokgibi> not work
[01:18] <yokgibi> it start with terminal directly
[01:19] <superm1> sounds as though its having trouble booting up to X then.  Not exactly an installer problem then -
[01:20] <yokgibi> in the tty1, it said : User not known to the underlying authentication module
[01:21] <yokgibi> i guess, cd may be corrupt, re-download iso
[01:21] <yokgibi> burn it again
[01:21] <yokgibi> and same as before
[01:21] <yokgibi> bo result
[01:21] <superm1> you can check the cd consistency in that menu
[01:21] <yokgibi> yes
[01:22] <yokgibi> in the first downloaded cd, there are 30 errors, re-downloaded cd 28 error
[01:23] <yokgibi> but i'm installed 3 months ago with this cd
[01:23] <btm> yokgibi: you may want to burn at a slower speed and see if you can get a good cd. Or your cdrom could have problems and you may want to try on another machine.
[01:23] <superm1> well having anything >= 1 will likely cause troubles
[01:24] <superm1> you can consider cleaning that cdrom drive
[01:24] <superm1> with some isopropyl alchohol or something similar
[01:24] <yokgibi> i ll try both solutions
[01:24] <yokgibi> thanks for alla
[01:24] <yokgibi> all
[01:24] <yokgibi> byes
=== mpt [n=mpt@121-72-128-43.dsl.telstraclear.net]  has joined #ubuntu-installer
=== metaxyy__fw [n=alex@c-24-63-216-122.hsd1.ma.comcast.net]  has joined #ubuntu-installer
[09:24] <metaxyy__fw> Is this an inappropriate venue to ask a question that's not directly dev-related, but addresses a behavior of the installer so obscure that probably only you guys would know?
=== blackskad [n=blackska@d54C4A53D.access.telenet.be]  has joined #ubuntu-installer
=== mpt [n=mpt@121-72-136-61.dsl.telstraclear.net]  has joined #ubuntu-installer
=== mpt [n=mpt@121-72-136-247.dsl.telstraclear.net]  has joined #ubuntu-installer
=== cjwatson [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk]  has joined #ubuntu-installer
=== Elwell [n=andrew@87.127.71.46]  has joined #ubuntu-installer
=== jakeg [n=example@ip-81-170-103-71.cust.homechoice.net]  has joined #ubuntu-installer
=== jakeg [n=example@ip-81-170-103-71.cust.homechoice.net]  has left #ubuntu-installer [] 
=== blackskad [n=blackska@d54C4A53D.access.telenet.be]  has joined #ubuntu-installer
=== superm1 [n=superm1@ubuntu/member/superm1]  has joined #ubuntu-installer
=== cr3 [i=marc@conference/oscon/x-78c3577439ebcac5]  has joined #ubuntu-installer
=== blackskad [n=blackska@d54C4A53D.access.telenet.be]  has left #ubuntu-installer [] 
[11:01] <btm> what package decides the /dev entry used by a block device? is it the kernel/module or udev?
[11:15] <cjwatson> btm: the kernel nominates defaults, but udev rules can (and often do) override them. Most udev rules are provided by udev, but some are provided by other packages.
[11:24] <btm> i'm trying to track down a bug where certain sd devices are coming up as eth devices in /dev in the feisty installer but work fine in feisty installed. I think I'm missing where that decision is made as I don't see anything relevant in /etc/udev/rules.d
[11:25] <cjwatson> *eth* devices?
[11:25] <cjwatson> you mean like eth0? that's impossible, they don't have device node
[11:25] <cjwatson> s
[11:26] <cjwatson> anyway, if there's nothing applicable in /etc/udev/rules.d, then the kernel default is used
[11:27] <btm> Haha. Well, I agree it's absurd, but the disks all show up in /dev/disk/by-id and they're all linked to /dev/eth2. Of course there shouldn't be a eth nodes in /dev, but somehow that's what it's getting named.
[11:28] <btm> Note that these are 3ware 9650se disks, and I don't see this issue on the 3ware 9550's.
[11:29] <cjwatson> udevinfo may help
[11:30] <cjwatson> e.g. udevinfo -n /dev/eth2
[11:30] <cjwatson> er
[11:30] <cjwatson> udevinfo -q all -n /dev/eth2
[11:30] <cjwatson> should be possible to use that to trace through udev rules by hand to figure out where it's coming from
[11:31] <cjwatson> (I would say it's pretty unlikely to be an installer bug as such though, even if it's biting the installer)
[11:32] <btm> right. (lp 127404). I don't know where the issue is, so I'll track it down myself. thanks for the hint.
[11:39] <cjwatson> good luck ...
[11:40] <cjwatson> I've dumped it onto udev for now