Linux

Why did I bake nouveau into the kernel? Well, there was an article on kernel-compiling in Linux Magazine, to celebrate the kernel's 25th birthday. It suggested that things that are always used (like the main network card) be compiled in, while less-often-used things should be left as modules. Since it's simply a matter of clicking a checkbox in the configurator, I took this to heart. I should've gone with "if it ain't broke, don't fix it" instead!

What sorts of problems have you with Wine? Perhaps I could help. I've a lot of experience with Wine now.

Your problems sound weird. What session manager were you using before you switched to command line, as a matter of interest?
I'm guessing your problems with compiling Awesome are related to outdated dependencies. What errors do you get? Are you sure they don't ship official DEBs for ARM?
 
Wine ? Well, the games don't start, and when they do they lag incredibly, even though I launch them with my GPU.
I had some error messages but for now it ain't my priority.

I forgot to mention that my Display Manager was LightDM that was configured to use PiX systematically, I tried KDM to see if I could get an Awesome window to run but still nothing.
About the error message I saw it inside the Cmake folder but I don't remember it, I'll post it here when I'll be less tired, like tomorrow. :)
And no, the deb is 3.4 for ARM, so I'll have to work on it to get it running, never simple heh ?
 
News time children !
The freshest infos of radio Wasteland, bringing the truth, no matter how bad it hurts.
So, I managed to compile Awesome! The problem was some missing build time dependencies, there was surely a lot missing, but I got it covered now.
I had to install the dev version of the packages to allow the compiler to load the necessary libraries, but fortunately it is done..
Oh wait a minute.
Nope.
I launched Awesome, and it worked, bringing up my computer desktop (I copied the config files of my desktop from my computer)
And I switched to the interface I had specially created for my PiP Boy, for some unknown reason, it fucked up, no log, no error message, just being thrown back to my desktop manager in order to launch a session.
Shite.
I still have to investigate but for now it is nearly 3 AM and I have to try to sleep, of course I'll keep that topic updated if I don't have to double post in order to do so.
Aside, I managed to get my camera module (barely, for now) working ! I made a small high resolution film. :)
I progress at a good speed, if I could solve a problem each day it should be finished soon enough.
On the hardware part now, I bought a bowman arm protection to fasten all the pieces together on it to make it a nice wrist computer, I still have to find some extra black leather straps but it should be done next week :)
 
No log, no error message? Did you try dmesg to see if there was a segfault involved? (There shouldn't be, but it's late here too so I'm just tossing out ideas.)
 
Urgh, I figured out what was the problem, for some reason, the compilation only installed a part of the packages, and Awesome keeps falling back to the old files, so I found a Stretch version of Awesome, but unfortunately to install it I have to update many, many packages to their stretch counterparts, I'll do that tonight.
 
What files did it not install? Did you try using ccmake to manually adjust the configuration?
 
Okay, so I did otherwise, I first try, as you said to configure Cmake, but it didn't worked, so I created a .deb with my build files, after comparing it with the Stretch build, the weight of the package was the same, so I'm pretty sure the problem comes from a frickin line of code absent in a file in order to reference Awesome as a window manager, any ideas ?
Also, launching it from the command line triggers it, but it can't be launched from there nor from an active session, strangely any modification into the Xinitrc changes nothing aside of turning my screen black.
Any ideas ? I'm pretty tired now, I spent all my night on that crap.
 
Just one line saying to launch Awesome, it works with all other WindowManagers.
I just rage quit on that, I spent my whole day on Window Maker, and it looks very good and actually has the vibes I wanted, the only problem is how obsolete the dockapps are.
I actually have two questions :
Do you know a way to force a number of DPI on a screen and
Where the hell am I supposed to find those X11R6 libs that are so 2005. (Need them to compile a dockapp)
I remember forcing 96 dpi on Slackware by using a xorg.conf.d file, but it seems to work differently here.
And actually you know the worst ? Awesome, I managed to accidentally make it run on LXDE today :facepalm: it shows up when I don't need it.
Also, I'll be uploading a picture of my proto PiP Boy tomorrow. :)
 
I promised it, here it is !
First, a picture of the WIP wrist mount straps (and items placement :
BP01NHg.jpg.png

And a picture of the Wip (without wires) screen and central unit :
XQhomvX.jpg.png

PluMGMK said:
http://cgit.freedesktop.org/xorg/lib for the X11 libs.
Click to expand...
Thanks but huhhhh, aren't they somewhere in my system ? I dunno like huh, in a new directory ?
PluMGMK said:
Wow, you abandoned Awesome after planning its use for so many months. How does that feel?
Click to expand...
Feels bad son... Bad. :pfff:
Although for the sake of the efforts I have put in this I'll try to make it work, if it worked by accident yesterday, it should work with a few workarounds, but at some point you get tired of things like that.
Now I can hear Shia LaBeouf making his speech in my head, thanks to you. :lol:
 
I wasn't thinking, so yeah. Of course they should be somewhere on your system. Doesn't pkg-config know where to find them? :?
 
News. Agh.
So, I have spent the last two days working on a "X free Font or color problem"
What it was ? I was unable to launch my dockapp, it just said something was missing, but for the life of me, I can't remember it's name, it's like a tip on my tongue. But I'll post it here as soon as I remember it.
So what have I done ? Spent hours and hours on a search engine, only to find severely outdated posts and issues, but I finally stumbled upon a reddit page about the beta of steam under Linux, some dude had exactly the same issue, and the app couldn't launch, so I followed his lead and basically installed all the fonts available the repository.
It. WORKED.
(A bit heavy though, ain't gonna lie)
The widgets are ready, and time maybe even brought me a solution to use Awesome.
I still have a problem that obsesses me, and I cannot think about taking a break without finding the solution.
See, I'm unable to launch apps at startup, normally it can be set in a file named autostart inside Windowmaker's directory (~/GNUstep) but whenever I modify it, it crashes the windows manager, making it unusable without commenting out the line
Any idea of how I could start programs at logintime ?
I have tried with an .xsession file, a .desktop file in ~/.config/autostart and in /etc/xdg/autostart
Seemingly, it works for all window managers installed on the machine but Window Maker.
Since you're using a lightweight WM I was thinking you could help me with this one.
Also, feel free to recommend me what I have already done, I may have made mistakes in the files.
 
Wayland my dear, all this X stuff feels archaic, alien and frightening to me! :fou: I wish I could be of more help. Are you getting no log output from Window Maker either?
 
So as I already implied in the You Game, my LFS system has been obliterated!

You see, Monday night I finally got the NVIDIA driver working! Since Xorg/kernel/etc. updates would require me to remove the proprietary driver (at least temporarily), I then proceeded to write a Perl script that could automate switching between drivers at boot-time. This is non-trivial, since a lot of libraries need to be installed/uninstalled (despite my initial naïve notions of what GLVND was capable of).
From the very start, I have had a primitive package-management system, which I kept telling myself I needed to overhaul. I install packages into a subdirectory of /root ( :!: ) and then tarball them up. To (re)install a package the files are extracted from the tarball back into that directory, then copied out onto the system. This procedure plays havoc with symlinks for some reason, so I decided I would stop using it for Mesa and GLVND, since screwed-up symlinks cause the X Server (or Mutter on Wayland) not to start when the NVIDIA driver is installed. Instead I would keep the (separate 32-bit and 64-bit) build directories of Mesa and GLVND, and just run "make install" in each to reinstall them. It makes sense since I'm always updating Mesa to the latest Git anyway, and package tarballs are just a waste of time for that.
I incorporated this newer strategy into my Perl script. However, there is one library that NVIDIA's driver overwrites that is supplied neither by Mesa nor by GLVND. It is part of the X Server. So I decided, rather than switching strategies for the X-Server, I would just incorporate my old package-manager into the Perl script for that one package (i.e. call the shell script I wrote last Christmas). I left a comment about symlinks "not screwing us over too much" or something to that effect. I was half-right. The symlinks didn't screw me over. But calling that shell script from a boot-time job was a fatal mistake!
You see, the shell script was rather shoddily written, and contained a glaring security hole. See if you can spot it: (Hint: environment variables are not set in the script itself, but assumed to have been set prior to running it)
STUPIDcode.png

That's right, ${IMAGE_DIR} can be anything at all, and at boot time is, of course, nothing at all! So the line is read as "rm -r /*". When this script was running, there was no graphics driver loaded yet, so I couldn't see what was going on. I noticed a lot of disk activity, which I assumed was the NVIDIA driver uninstalling itself. Eventually I cut the power and rebooted into Debian to see if I could refactor my code. But then I discovered the code wasn't there anymore! Neither was my home directory! Of course, the shoddily-written package-management script survived, hence the annotated screenshot above; the irony is delicious.

Right now, I am running TestDisk to recover my data. There is no directory structure in the recovery, which means I can't rebuild the system, but I will hopefully at least be able to find all the decent Perl code I wrote, and cat pictures and stuff.
The plan now is to build a new LFS system starting on Saturday, and finally implement a better package-management solution (the principle will be the same, but the scripts will be more rigorous, and the storage locations won't be inside /root, and stuff like that). These improvements to package management will be the silver lining to this whole thing. I'm just hoping all the experience I've gained will mean it won't take as long to get up and running as it did last time!
 
Poor you, I know how losing important stuff feels. :( Hope your data gets recovered!
 
Thanks! I'm fairly sure it will, but those Perl scripts might not come back as separate files…
 
I'm gonna be totally honest, I laughed a little bit when I readed rm -r /* That was too n00b dude.
Damn son, that's the definition of "Epic Fail" you just defined here, although I can understand what you had in mind while doing that.
One Linux proverb says "There's two kind of SuperUsers : The one that made the mistake, and the one about to make it".
Holy shock man, that's surely an awful amount of time and data that you wasted here, and just when it is about to be the anniversary of the day where you installed LFS.
Save yourself some time and install Slackware, or if you feel a tad masochistic, make yourself some Gentoo.
I know how it feels man, although it must feel even worse when loosing the data you actually created.
 
Hey I know, believe me! :)
Look, I know what you're saying about Slackware and Gentoo, but at this point I think I wouldn't really feel like I was in charge without having compiled every single thing myself. I want to do it, and the holidays are much better timed this year, so I don't think I'll end up spending Christmas on getting it working like I did last time. :)
 
You must log in or register to reply here.
Back
Top