[00:25] slangasek: in saucy, linux-libc-dev:i386 and linux-libc-dev:powerpc cannot be installed at the same time :/ [00:26] hmm, really? they're at the same version [00:26] so they ought to be [00:27] BenC: pastebin me some apt output? [00:51] slangasek: http://paste.ubuntu.com/6423974/ [01:01] slangasek: so a version mismatch of 3.11.0-12.19(ppc) and 3.11.0.13.20(i386) will make it uninstallable? [01:01] Seems so...I can install it now [01:01] SRU mismatch [01:11] slangasek: libc6-dev conflicts now (installing :powerpc removes :i386) [01:11] slangasek: how I can get apt-get to show how it's depsolving this? [01:11] It's the same version, too [01:12] apt-get -o Debug::pkgProblemResolver=yes ? [01:14] slangasek: And sorry, it's libc6-dev:amd64 it is conflicting with [01:14] still shouldn't conflict - but they do have to be at the same version [01:16] They are the same version. [01:16] hmm [01:16] what does 'apt-get install libc6-dev:amd64 libc6-dev:powerpc' say? [01:16] It appears part of the problem has to do with libc6-dev-powerpc-cross [01:16] ah, hmm [01:17] http://paste.ubuntu.com/6424041/ [01:21] ok, that's odd [01:21] and an 'apt-get -f install' doesn't fall over, or something? [01:27] slangasek: tries to upgrade linux-libc-dev:amd64, but that's all [01:27] ah, so you probably need that upgrade to happen first [01:27] and then the rest of the conflicts should just go away [01:28] If I upgrade that, it removes linux-libc-dev:powerpc [01:28] Because then it doesn't match versions [01:28] hum [01:28] well, you need them to be matched [01:29] linux-libc-dev:(amd64|powerpc) are matched on the system right now [01:29] And everything is satisfied [01:29] but 'apt-get -f install' wants to upgrade it? [01:29] that's strange [01:29] You're right, that is strange, but it gave me no problems on downgrade [01:29] this is amd64? [01:29] (the main architecture) [01:30] $ dpkg --print-architecture [01:30] amd64 [01:30] why can you not upgrade both :amd64 and :powerpc? [01:31] Oh, wait! [01:31] Maybe I should add powerpc updates and security :/ [01:31] aha [01:31] yes :) [01:34] Damnit...that fixes the linux-libc-dev problem, but still won't let me install libc6-dev:powerpc [01:35] slangasek: apt-get -f install [01:35] Now shows nothing [01:35] No upgrades available [01:46] slangasek: I've purged all the powerpc packages...starting from scratch...what's the main package to install to get this rolling? [01:54] slangasek: So the main thing is I can install a cross build environment without problems, base build...but to install libncurses5-dev:powerpc requires linux-libc-dev:powerpc (as opposed to linux-libc-dev-cross-powerpc) [01:55] There is no complimentary libncurses5-dev-cross-powerpc :/ [03:38] slangasek: so "apt-get install libc6-dev:powerpc" wanted to remove gcc, but "apt-get install libc6-dev:powerpc gcc" allowed it to install without issue [03:38] slangasek: Sounds like a problem in apt-get's dep solver relating to Multi-Arch [04:12] I have an old laptop that I upgraded to saucy and it will only boot the earlier 3.8 kernel. The 3.11, including the proposed, hangs on "Platform eisa.0: Probing EISA bus 0" I also tried the 3.12.0-999 kernel at http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ Any suggestions? [14:11] linuxtech, you should file a bug with 'ubuntu-bug linux' and let us know the number, note in the description that the version you are reporting on works, and which versios you have tried which do not. we can then suggest some versions to try to identify where the issue was introduced [19:06] hello everybody, i need help for my other pc, because i cant boot anymore after kernel-test-phase [19:09] this is the mail after i have reported to launchpad: http://paste.ubuntu.com/6376813/ [19:10] please help!! [19:14] The main problem is because of the fail load of fallback graphics devices [19:14] any idea? [19:15] what is your gpu? [19:15] jovando: selecting another kernel in the boot menu doesn't work? [19:16] yes it doesn+ [19:16] t [19:17] wait, you're using Netrunner, not Ubuntu? [19:18] before testing a new kernel (according to kernel team or launchpad) the last kernel i could use was the kernel "Netrunner, with Linux 3.2.0-52-generic-pae" [19:19] after installing the test kernel i was able to boot one time to KDE but after a recommended restart -> no kernel work any more because of the fallback graphic devices *fail* [19:20] "VGA compatible controller [0300]: NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 [VGA controller])" [19:20] yes and they forwarded me to ubuntu-kernel forum, because this is a kernel-issue [19:21] yes this is my graphic card [19:22] does anyone have any idea to prevent the fail of fallback graphic devices? [19:22] jovando: I'm not sure if Netrunner has different kernels from Ubuntu's? [19:24] JanC do you have the non free driver for nvidia installed? [19:25] and I am assuming nouveau would be installed in your system [19:25] i am also not very good at linux issues, because i use linux since 2 years (just for information) [19:25] I started in 2005 [19:25] i dont know if there are different kernels - the next is that i use a pae kernel version [19:25] and I am not yet good at all issues although I used several families of distributions over time [19:26] at "additional drivers" i have installed the recommended driver [19:26] i think version 347 [19:26] jovando: one problem is that you seem to use Netrunner, not Ubuntu, and this is a channel for Ubuntu; maybe there is a channel for Netrunner somewhere? [19:26] jovando do you have nvidia non free blob or not? If you do, you could start a live, chroot and remove the nvidia (apt-get autoremove --purge -y nvidia) [19:26] i dont know if this was a non-free driver.... [19:27] jovando what does the error in /var/log/Xorg.0.log say? [19:27] if Netrunner is enough like Ubuntu, that might work... [19:27] what is nouveau? [19:27] jovando try this command: [19:27] nouveau is the free driver [19:27] and it works (now) [19:28] so your system might meet with a conflict between drivers, so for the testing purposes at least you should remove nvidia driver [19:28] if you have it installed [19:28] netrunner is very similar a kubuntu version [19:29] you should look from within a live cd or live usb if you find the error messages related to "Driver" in /var/log/Xorg.0.log [19:29] jovando just do that, boot to live and have a look, then if you have nvidia installed, just remove it [19:29] you know how to chroot probably? [19:29] ok, the problem is i cant boot - how can i look and report the "Driver" in /var/log/Xorg.0.log ? [19:30] and mount and or bind /dev to dev/ and such? [19:30] jovando with a LIVE CD [19:30] I just told you [19:30] sry, what does chroot means? [19:31] jep, sry one moment i will try [19:32] https://help.ubuntu.com/community/LiveCdRecovery [19:32] chroot means you change the root [19:32] when the partition / is mounted, to /media for example [19:32] then you cd to /media [19:32] ok, cd boot now ... [19:32] then the command "sudo chroot ." will get the / of the distro which is in the hdd at the level of the / of the live [19:33] from within the console of course [19:33] you have to mount a few more things first so that what you will do in the chroot is well registered in the system [19:33] I think this is appropriate: [19:33] mount none -t proc /proc [19:33] mount none -t sysfs /sys [19:33] mount none -t devpts /dev/pts [19:33] ok, it needs a little bit time - still booting [19:34] once the / of the hdd mounted to /media of course [19:34] jovando take note [19:34] thanks in advance for advise [19:34] of the two following links: [19:34] https://help.ubuntu.com/community/LiveCdRecovery [19:34] I don't know the mount and bind relevant commands by heart so I go to that page to find them again when in need: [19:34] https://help.ubuntu.com/community/LiveCDCustomizationFromScratch [19:35] if you meet with error messages about other directories not mounted when you will be in the chroot just leave the chroot by typing "exit" in the console, and add the missing mount point, then again chroot [19:36] just pay attention : /dev is not the same thing as dev/ : according to where in the system you are located from within the console [19:36] once chrooted, you can seek for nvidia in the chrooted system, ie with a command such as "dpkg -S nvidia" [19:36] if you see a long list then it means it is installed [19:37] ok, i try the point: Update Failure [19:37] if you just type "apt-get autoremove --purge -y nvidia" and it does remove nvidia and packages it is as good [19:37] I am hurrying because it's almost time for dinner her [19:37] here [19:37] I don't know what is "Update Failure" ? [19:38] under you first link: https://help.ubuntu.com/community/LiveCdRecovery [19:41] jovando this first link is just to tell you how to use a live cd, all the rest may not refer to your present case [19:42] while I'm here I have a general question, does someone know how long the SRU process can be before a patch committed by someone hits the newer kernel coming in the repos? [19:42] I have a concern about the 3.2.0 serie for Precise because I can't use zram-config with it [19:43] what does SRU process mean? [19:44] https://wiki.ubuntu.com/StableReleaseUpdates [19:44] thanks google "SRU Ubuntu" ;-) [19:47] i can just say that approx. every 2 weeks i have to update my kernel over the repos, but you mean something different, don't you? [19:53] ok, i have studied the links [19:54] now you recommend to purge via: apt-get autoremove --purge -y nvidia? [19:57] have a good snack first, melodie :-) [20:01] ok, so first i have to change root before i can purge? [20:04] can anyone give me advise what to do next? [20:07] or can somebody give me advise to chroot? [20:10] Do i need the packages "Casper" and "debootstrap"? [20:16] i found another way to purge, but the console says: E: Unable to locate package nvidia [20:16] what can i use instead of: apt-get autoremove --purge -y nvidia? [20:19] jovando reread what I told you: [20:19] mount the system partition, do the necessary bindings, then chroot to be *inside* the system [20:19] then type your remove command line [20:20] i try but i am also not so good in english [20:20] jovando if you don't talk English of French I can't help more :) [20:20] being good in English will come with practice, don't worry about that [20:20] i try my best [20:21] ok, i am booting now the live cd again [20:22] so i am at gui of live cd [20:22] the link says i need casper for chroot,,? it's a little bit difficult for me to know what i need to solve the problem [20:24] ok, now i have also internet on live cd [20:26] i think i have mounted the hard-disks now [20:28] i think i have chroot with sudo, the only problem is that the nvidia package is unable to locate [20:28] do you know what to do in this case? [20:33] apw: bug https://bugs.launchpad.net/bugs/1251816 Boot failure with saucy kernel 3.11 probing eisa [20:33] Launchpad bug 1251816 in linux (Ubuntu) "Boot failure with saucy kernel 3.11 probing eisa" [Undecided,Confirmed] [20:39] jovando you don't need casper to chroot /o\ [20:40] jovando if you chrooted then do this command now: [20:40] grep Driver /var/log/Xorg.0.log and paste the result to http://pastebin.com [20:40] then bring back the url [20:41] grep will filter and seek the word Driver in the Xorg.0.log file which is under /var/log and we will see what it says [20:41] or you could as well copy the whole file Xorg.0.log to pastebin and I will look [20:42] ok, om [20:43] jovando ping me once done, I'll be talking on other chans too [20:45] http://paste.ubuntu.com/6428411 [20:47] ok [20:48] jovando from lines 14 to 26 it shows you have the nouveau driver in action. so do just the reverse that I told you: install the non free driver nvidia and remove nouveau driver and nouveau firmware [20:48] then reboot once or twice [20:48] the package name you will find with "dpkg -S nouveau" [20:48] package names* [20:48] install nvidia first [20:49] I think the nvidia current version should do, perhaps checking this detail at geforce website would help ensure it is correct [20:50] this is the hole file of Xorg.0.log: http://paste.ubuntu.com/6428428 [20:51] jovando ok so don't do what I just said [20:51] look at lines 107 to 110 [20:51] and then I'll explain what I think [20:53] make sure you got the kernel headers [20:53] ok, so the module does not exist [20:53] no no [20:53] not just that [20:53] ok, just one information in advance: i am still in live boot - is this ok? [20:53] the last file is not complete [20:54] you might want to install pastebinit and do "pastebinit /var/log/Xorg.0.log" [20:54] yes, you need to be in the live boot in chroot in a console to be inside the system which is on the hard drive [20:55] in the chroot type "apt-get install pastebinit [20:55] " [20:55] without the quotes of course [20:55] tell me if you can install it? [20:55] ok, so i already used chroot and i wasnt aware of that? [20:55] aware of what? [20:56] that i chroot [20:56] i didnt installed anything of that what was in your link - i just used sudo [20:56] well when you are in a swimming pool under the water with a diving equipment you are aware where you are, right? [20:57] when you are in a chroot you are root [20:57] so you don't need sudo [20:57] when you are in a chrooted system in a console you have the # at the end of the prompt [20:57] and when you type "ls" you see all the directories which are inside / in your hard drive. Is that ok ? [20:58] in the normal live system when you open a console you are in /home/ubuntu : is that ok so far? [20:58] the # isnt here, but i can see all in the system with ls - this is how i reported the xorg.0.log file [20:59] the # must be there [20:59] if you report the wrong file system it is meaningless [20:59] http://paste.ubuntu.com/6428428/ [20:59] your prompt does not show [21:00] I'll chroot one of my own systems and paste the result to show you [21:00] at this here: http://paste.ubuntu.com/6428411/ [21:00] I will chroot this one: [21:00] /dev/sdb3: LABEL="MiniBuntu" UUID="2faa1046-6563-4f33-b82c-ce316f35664a" TYPE="ext4" PTTYPE="dos" PARTUUID="000c3e38-03" [21:01] there: is "netrunner@netrunner:~$" [21:01] not good [21:01] you are user in the live system [21:01] what do you do to know so much about that? [21:01] we need to be root inside the system [21:02] ok, i hope it is not complicated to chroot [21:02] I have been using and learning since 2004 without stopping one day, you don't want to know all about the file system and all tips and tricks just in two years, do you? [21:02] how can i do that? [21:02] it is not once you will have understood the principle, just look at the example I will provide now and you might get it instantly [21:02] I will chroot this one: [21:02] /dev/sdb3: LABEL="MiniBuntu" UUID="2faa1046-6563-4f33-b82c-ce316f35664a" TYPE="ext4" PTTYPE="dos" PARTUUID="000c3e38-03" [21:03] [joyce@squirrel:~]$ sudo mount /dev/sdb3 /mnt [21:03] i learnt much, but the terminal commands are not so easy for me... [21:03] [joyce@squirrel:~]$ [21:03] just read please, for now and stay focused [21:03] now my mini buntu is mounted to the /mnt directory [21:04] $ cd /mnt [21:04] $ [21:04] $ls [21:04] bin dev home lib media opt root sbin srv tmp var [21:04] boot etc initrd.img lost+found mnt proc run selinux sys usr vmlinuz [21:05] let's say I have done the mount and bind necessary to have the /dev partition under /mnt populated [21:05] or not: I will do the mount commands [21:05] $ sudo mount -o bind /dev dev/ [21:05] i can i find out which disk to mount? [21:05] $ [21:06] with "sudo blkid" you will get information about all partitions available, be they mounted or not mounted [21:06] $ sudo mount -o bind /sys/ sys/ [21:06] $ [21:07] $ sudo mount -o bind /dev/pts dev/pts/ [21:07] $ [21:07] next is just typing: [21:07] $ sudo chroot . [21:07] the . means "here" [21:07] now my prompt is this : root@squirrel:/# [21:08] the # pwd command tells me where I am: [21:08] root@squirrel:/# pwd [21:08] root@squirrel:/# [21:08] ok, but first i have to do the sudo mount -o bind ... [21:08] ? [21:08] I have "CHanged Root" [21:08] chroot [21:09] ok, so easy :-) [21:09] i am root now [21:09] with the # [21:09] yes, because it will allow populating the /dev partition of your system in hdd and it will allow for some logs to be updated when you will install or uninstall some components [21:09] jovando you see? A good example is better than a long explanation [21:09] jep :-) [21:10] check if you are having the network connection, do a ping to google.com for instance (in the chroot) [21:10] http://paste.ubuntu.com/6428531 [21:11] I am not sure I provided all the mount commands necessary but if you see a message error later it will be easy to correct and add a missing mount (by exiting the chroot, adding the missing mount point and chrooting again) [21:11] yes i have ping of approx. 200 [21:12] something is wrong in your pastebin [21:12] very wrong [21:12] I will comment line by line [21:12] netrunner@netrunner:/$ sudo mount /dev/sdb3 /mnt [21:13] you have assumed that your /dev/sdb3 is the same as mine. Huge error, in your partition it is a Windows install or other Windows partition [21:13] as says the sentence: [21:13] "Mount is denied because the NTFS volume is already exclusively opened. [21:13] The volume may be already mounted, or another software may use it which [21:13] could be identified for example by the help of the 'fuser' command." [21:14] (I should get paid for a full course) [21:14] jovando you were already in the / of the live: [21:14] netrunner@netrunner:/$ sudo blkid [21:14] see ? [21:14] netrunner@netrunner:/$ [21:14] yes you should get paid :-) [21:15] and from there you have just chrooted ! [21:15] i can send you via ... anything [21:15] you didn't even read the warning ! [21:16] here is not the good chan for a full course, come to #linuxvillage and I might point to a Free software actor where you can send a little donation if you are willing to [21:18] jovando: i dont think that this fits into the kernel channel. its very low level support asked from you: see this german ubuntu chroot howto http://wiki.ubuntuusers.de/chroot/Live-CD [21:18] i think i know what you mean [21:18] and again: no guarantee that this works with netrunner OS. i would suggest to talk to their support [21:18] i should mount the right partition first - then i go in with chroot [21:18] right? [21:19] should we go an in the other channel now? [21:34] k1l_ it's ok I take it from here with jovando on my chan dedicated to all topics