| [02:38] * lamont2 wonders why this stupid machine doesn't like to read DVDs | |
| [02:39] <lamont2> and somehow I bet that upgrading from -14.46 to -14.47 won't make a diff | |
| === asac_ is now known as asac | |
| === doko_ is now known as doko | |
| [08:57] <kraut> moin | |
| === tku is now known as kraut | |
| [13:36] <Kano> hi, could somebody fix the rt73 driver in 2.6.24? | |
| [13:37] <Kano> also why is always 1 the default for | |
| [13:37] <Kano> + # Oh hell, give 'em one | |
| [13:37] <Kano> + ifeq ($(CONCURRENCY_LEVEL),) | |
| [13:37] <Kano> + CONCURRENCY_LEVEL := 1 | |
| [13:37] <Kano> + endif | |
| [13:37] <Kano> i would prefer 2 or 4 | |
| [13:38] <Kano> multicore cpus are standard | |
| === chuck is now known as zul | |
| === rikai_ is now known as rikai | |
| === XSource_ is now known as XSource | |
| === \sh_away is now known as \sh | |
| === \sh is now known as \sh_away | |
| === chuck_ is now known as zul | |
| === macd_ is now known as macd | |
| === \sh_away is now known as \sh | |
| === \sh is now known as \sh_away | |
| [19:12] <bdmurray> mdomsch: I have a question about the dell firmware updates | |
| [19:12] <bdmurray> mdomsch: there doesn't seem to be a bios for the dimension 9150 is there a reason it is missing? | |
| [19:28] <mdomsch> bdmurray, what does 'getSystemId' return for that system? | |
| [19:28] <mdomsch> and is it an AMD? | |
| [19:37] <bdmurray> mdomsch: Error getting the System ID | |
| [19:37] <bdmurray> and it is an Intel | |
| [19:42] <mdomsch> eww | |
| [19:42] <mdomsch> hm, try running as root | |
| [19:43] <bdmurray> that helped ;) - System ID: 0x01D1 | |
| [19:45] <mdomsch> ok, then run the whole aptitude line, being sure you're root when you execute bootstrap_firmawre | |
| [19:50] <bdmurray> I received lots of "Couldn't find any package whose name or description matched" | |
| [19:55] <bdmurray> mdomsch: http://pastebin.ubuntu.com/3291/ | |
| === \sh_away is now known as \sh | |
| [19:59] <mdomsch> bdmurray, :-( | |
| [19:59] <mdomsch> no, that won't work | |
| [19:59] <bdmurray> mdomsch: that's what I thought too | |
| [20:00] <mdomsch> sudo aptitude install $(sudo bootstrap_firmware -a) | |
| [20:00] <mdomsch> notice the second sudo | |
| [20:00] <mdomsch> that's critical | |
| [20:00] <bdmurray> could you update the wiki then? | |
| [20:00] <mdomsch> (I understand why people don't like 'sudo bash, ...' | |
| [20:00] <bdmurray> http://linux.dell.com/wiki/index.php/Repository/firmware#Downloading_firmware | |
| [20:01] <bdmurray> oh, that's right | |
| [20:01] <bdmurray> the wiki assumes that you are root right? | |
| [20:01] <mdomsch> yeah... | |
| [20:01] <mdomsch> yeah | |
| === alleeHol is now known as allee | |
| [20:01] <mdomsch> that's why I don't put 'sudo' in front of all those lines | |
| [20:02] <mdomsch> you're not the first to have run into this - it happens pretty often | |
| [20:02] <mdomsch> so I need some way to highlight _hey - run all these in a 'sudo bash' shell first..._ | |
| [20:02] <bdmurray> and it isn't the first time I have run into either | |
| [20:03] <bdmurray> maybe if you put a prompt there it would be clearer | |
| [20:03] <bdmurray> root@bob:# or something | |
| [20:03] <mdomsch> yeah, I wanted something that could be cut-n-pasted into a script | |
| [20:03] <mdomsch> or a shell directly | |
| [20:05] <bdmurray> so now I should have a new firmware in /usr/share/firmware/bios/ ? | |
| [20:05] <bdmurray> and update_firmware will install it? | |
| [20:08] <mdomsch> yes | |
| [20:09] <bdmurray> I don't actually have a /usr/share/firmware directory | |
| === Lure_ is now known as Lure | |
| [20:10] <mdomsch> hmm, did aptitude download a system-bios-* package? | |
| [20:10] <bdmurray> It doesn't seem that way | |
| [20:12] <mdomsch> you should have gotten system-bios-dxp051_0.a07-1_all.deb | |
| [20:15] <mdomsch> because that's what provides system-bios-ven-0x1028-dev-0x01d1 which is what the aptitude + bootstrap_firmware command requests | |
| [20:16] <bdmurray> okay, I think I have a better understanding of how it is supposed to work and will try and work it out | |
| [20:17] <mdomsch> sudo bootstrap_firmware -a should include a system-bios-* line in it | |
| [20:17] <mdomsch> in its output that is | |
| [20:17] <mdomsch> if it doesn't, that's bad | |
| [20:18] <mdomsch> that comes from the firmware-addon-dell package being installed | |
| [20:20] <bdmurray> I seem to be having some troubles with the wget .. bootstrap.cgi bit but those may be related to aptitude | |
| [20:24] <mdomsch> again, you need to run the output of bootstrap.cgi into a sudo bash shell | |
| [20:25] <mdomsch> it configures /etc/sources.list.d/ entries and GPG keys for same | |
| [20:25] <bdmurray> yeah, I got that bit down now | |
| [20:25] <mdomsch> if that didn't run, then you won't be hitting linux.dell.com to look for packages | |
| [20:34] <bdmurray> I've narrowed it down to dell-repository-keys being untrusted | |
| [20:38] <bdmurray> and I have the libsmbios gpg-key installed | |
| [20:39] <mdomsch> bdmurray, apt-key list shows the libsmbios signing key? | |
| [20:39] <bdmurray> yeah, I'm on hardy by the way | |
| [21:05] <bdmurray> mdomsch: Am I doing something wrong? | |
| [21:05] <mdomsch> bdmurray, pls pastebin exactly what you've typed so far | |
| [21:05] <mdomsch> it should be as simple as I describe on the web page | |
| [21:06] <mdomsch> firmware-addon-dell is installed from the hardy repo, as is firmware-tools | |
| [21:06] <mdomsch> only system-bios-* should come from the linux.dell.com repo | |
| [21:08] <bdmurray> mdomsch: http://pastebin.ubuntu.com/3292/ | |
| [22:00] <mdomsch> bdmurray, ok, I see your problem | |
| [22:01] <mdomsch> It seems the dell-repository-keys package and dell-firmware-repository, dell-software-repository packages aren't getting installed | |
| [22:02] <mdomsch> because aptitude is throwing up a prompt that the shell script doesn't expect, and thus the piped input fails to acknowledge the prompt | |
| [22:02] <mdomsch> soren, no dell-firmware-repository package | |
| [22:02] <mdomsch> (ooops, nick completion error) | |
| [22:02] <mdomsch> so nothing for bootstrap_firmware to find | |
| [22:06] <bdmurray> mdomsch: so I could work around it by manually installing those then? | |
| [22:06] <mdomsch> yeah | |
| [22:06] <mdomsch> seems I should make the aptitude calls take --assume-yes | |
| [22:09] <mdomsch> ok, bootstrap script now uses --assume-yes | |
| [22:09] <mdomsch> so just try that again | |
| [22:09] <bdmurray> okay, will do thanks | |
| [22:09] <mdomsch> hang on, let me push that... | |
| [22:13] <mdomsch> bdmurray, ok, try now | |
| [22:20] <bdmurray> mdomsch: it is still aborting because they are untrusted | |
| [22:28] <\sh> guys, important problem for everybody using hardy and xfs partitions:) please have a look at bug #180157 thx :) | |
| [22:28] <ubotu> Launchpad bug 180157 in linux "XFS root filesystem - install fails with "noexec or nodev" error" [Undecided,Confirmed] https://launchpad.net/bugs/180157 | |
| [22:39] <mdomsch> arrgh | |
| [22:39] <mdomsch> not sure how to solve that in bootstrap then | |
| === clever_ is now known as clever | |
| [23:15] <mdomsch> bdmurray, I'm upgrading my test box to hardy, and will try to find time this weekend to come up with something. | |
| [23:15] <mdomsch> maybe it'll be: | |
| [23:15] <mdomsch> wget -O bootstrap.sh http://... | |
| [23:16] <mdomsch> sudo bash bootstrap.sh | |
| [23:16] <mdomsch> (hit Y when prompted) | |
| [23:16] <mdomsch> worst case that'll be it... | |
| [23:16] <mdomsch> poke me on Monday if I don't have it fixed | |
| [23:19] <turbotorben> hi | |
| [23:19] <turbotorben> is it possible to get a uvesafb framebuffer working with the latest ubuntu kernel? | |
| === \sh is now known as \sh_away | |