=== st00p1d_ is now known as st00p1d === gnomefre2k is now known as gnomefreak [13:37] What do you think of bug 226431 ? Does it contain enough information for you to decide what could be wrong or should I have asked for more information? [13:38] https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/226431 [13:49] acx111 seems to be utterly broken [13:51] I poked through it briefly but couldn't figure out what the issue was [13:51] Yes, it'll just oops the machine when joining wpaed networks - didn't test unencrypted [13:51] should I give it the kernel-oops tag? [13:55] Does that require there to be an oops attached? If not, then go for it [13:56] I'll check for it at the wiki page === asac_ is now known as asac [17:15] Driver 'sd' needs updating - please use bus_type methods [17:15] Driver 'sr' needs updating - please use bus_type methods [17:15] then hard lockup on boot [17:16] http://pastebin.com/m31bc6bcd [17:20] Almost certainly unrelated [17:20] Well. In fact, completely unrelated. [17:21] well, it seems to be using the scsi driver for the ide now, and it finally drops to busybox and says /dev/hda1 does not exist [17:22] so maybe it is unrelated... or maybe it is why there is no root filesystem [17:22] Does sda1? [17:22] yep [17:23] So why are you trying to use hda1? [17:23] I dunno that's what it used to be called :) [17:24] We've been using UUIDs for ages [17:25] yeah I need to make an image to clone multiple of the same devices [17:25] so I take out the UUID and it used to be /dev/hda but I'll try /dev/sda now [17:26] Why would that stop you using UUIDs? [17:27] ... because I would have to type in the UUID to every device? [17:27] If you're using the same image, then it'll be the same UUID [17:29] really?? [17:29] I don't remember why but that did not appear to be the case [17:30] The UUID is part of the filesystem [17:30] So if you're imaging the same data onto multiple drives, then the UUID will be the same [17:31] In any case, this isn't a kernel issue [17:31] yeah [17:31] but why does it say the driver needs updating [17:31] and what is it using if not bus_type methods... [17:33] It's just a reference to the internals of the driver model in recent kernels [17:34] The old code is still prseent and used - it's just to remind people that these drivers should be updated to use the new methods instead, so the old ones can be removed === elmargol_ is now known as elmargol [17:34] mjg59, thnx I'll just recompile them from the latest then [17:35] Why? [17:35] They work fine [17:36] but they should be faster with the bus_type methods [17:36] and that is my root filesystem [17:36] so I don't exactly want errors/warnings/outdated code [17:36] No, they shouldn't [17:37] ok then :) [17:37] It's not a reference to code used in the i/o pathway at all [17:37] I wish we could all agree on some type of naming convention for errors that are errors, and errors that everyone can ignore :) === gnomefre1k is now known as gnomefreak [19:30] Ubuntu Hardy | Linux SGC-Atlantis 2.6.24-17-generic | FritzBoxWLAN Stick | Does not work. PLEASE HELP OUT! [19:31] it makes the system freeze/unstable/unable to shutdown .. and still does not connect [19:31] everything default === thegodfather is now known as fabbione === TheMuso_ is now known as TheMuso