Giving killX some love

Forum rules
Share your brain ;)
machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Fri Oct 04, 2013 12:00 pm

^ But, but, but ,,, Emacs *does* start even though Xpm cannot be found, by using ... err, you should know, either the daemon and then emacsclient, or emacs-24.1-noX (forgot the name, maybe already 24.2). Of course killX is noX, as the name suggests. :D

I like your zimgur script. Would you shared it sometime, please?
..gnutella..

User avatar
xaos52
The Good Doctor
Posts: 190
Joined: Thu Aug 15, 2013 11:59 am
Location: Eernegem, Belgium

Re: Giving killX some love

Unread post by xaos52 » Fri Oct 04, 2013 12:50 pm

Oh, sorry if that is so, but I was under the impression that emacs did not start at all. Maybe brain rot. I can't verify it now. Anyhow I have now a - much thinner - no-X emacs running.

zimgur is in my github repo now.
Connected. Take this REPL, brother, and may it serve you well.

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Fri Oct 04, 2013 12:58 pm

Yes, it doesn't start as 'emacs' (known reasons), but with adding the version-number and -nox -- that was actually the reason I made the daemon start up at boot. Linking an alias didn't look good, and at the time of creating killX they even bumped emacs24.1 to emacs24.2

Thanks for the script, will be of use :)
..gnutella..

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Tue Oct 15, 2013 8:17 pm

Created the partition, did wget killX. I'm still doing the tar thing on killX tar.bz2. My old Aspire is giving me hate more than love, I can feel it in the fan running like crazy. Don't know if tonight I'll be able to boot into it, but I'll treasure the info in this topic for tomorrow.

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Tue Oct 15, 2013 8:29 pm

Ok. I did manage to finish the tar thing. Updated grub and rebooted.
Yeah! I can see killX in my grub!
Chose killX and now I got a blinking cursor and laptop fan running like crazy again.
Too tired now to sort this out, but I hope it is not hardware related cause I haven't got another spare machine to try killX at the moment.

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Tue Oct 15, 2013 9:09 pm

Just figured it out. I need something I can run slackware64 on. The Debian Sid I got on this Acer is i686 and so I can't even run xaos52 fine chroot scripts (you know, that "Exec format error" bad guy).

I won't give up, of course. I blame my Acer and I blame me for not checking if the hardware was good for killX before trying. I'll make room for killX on the ThinkPad I got for our school, though I have to figure out how to hide it from my wife (cause the Thinkpad is supposed to be for our school, not for my "geeky stuff").

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Tue Oct 15, 2013 9:46 pm

get an older kernel or compile one yourself, or check htop - maybe gpm is causing high cpu. for me it does.
..gnutella..

User avatar
rhowaldt
Dog
Posts: 4565
Joined: Wed Oct 17, 2012 9:01 am
Contact:

Re: Giving killX some love

Unread post by rhowaldt » Wed Oct 16, 2013 8:50 am

i have noticed that when you just do not reply to Gekko, he will eventually figure it out himself ;)
All statements are true in some sense, false in some sense, meaningless in some sense, true and false in some sense, true and meaningless in some sense, false and meaningless in some sense, and true and false and meaningless in some sense.

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Wed Oct 16, 2013 9:56 am

^ lol well, I like trying everything I can before bother you guys ;)

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Fri Nov 15, 2013 11:52 am

I never give up (and never surrender, quoting Galaxy Quest), so I'm on it again.
Since my wife took the laptop I was working on with LFS for today, I went back to killX.
I put it alongside my lovely Elektra, fixed /etc/fstab and I can boot in! Yeah. I suppose all the work on LFS paid off well, cause I was able to boot on killX in few minutes with no problem. None of the issues I had above.

Now, let me figure two things out:

- make my wireless work properly
- take a screenshot of this beauty

And I'll come back with a proper scrot.

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Fri Nov 15, 2013 1:39 pm

I am fucking proud of you, son!
..gnutella..

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Fri Nov 15, 2013 1:46 pm

Thanks :)
I still have LFS going on, but today I'll try to set up killX properly.

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Fri Nov 15, 2013 1:54 pm

^ Should not be a big problem. The /etc/init folder is your friend. Network configuration is pretty easy if you have DHCP enabled, else you have to manually set up a few things. Unfortunately Ceni won't do :)
..gnutella..

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Fri Nov 15, 2013 6:07 pm

Some updates on my journey. Not surprisingly, turns out I'm a sucker.
Let's see. I used dhcpcd and eth1 worked out of the box. Then I grabbed b43-fwcutter and b43-firmware. Same stuff I got on Elektra (where I'm writing this right now via wireless network, of course). At boot, dhcpcd finds eth1 and gives a nice IP address to it. Then wlan0 comes up, but carrier gets lost, the old friend timeout shows up and wlan0 skipped.
Next step, I had a look at /etc/rc.d/rc.inet1.conf. There I put everything I suppose should be necessary for my wireless. No luck here.
I went with /etc/wpa_supplicant. Same bad luck.
So I grabbed wicd (and all its python, dbus-python, pygobject, etc. dependecies) via slackpkg. Fired up wicd-curses and the message "No wireless networks found" welcomed me.
Patience is the key. I'll come back to it later.

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Sat Nov 16, 2013 1:48 am

The Journey to Bloat started by adding wicd :) Don't need it actually:
http://www.slackwiki.com/Broadcom_Wireless
I don't know exactly which your BC adapter is, but probably you would have just needed to blacklist the kernel-built-in b43 modules and use the wl drivers instead, from the broadccom staging drivers.

sbopkg -i broadcom-sta

in /etc/modprobe.d/blacklist.conf add
blacklist ssb
blacklist b43

Of course you remove the b43-packages before.
..gnutella..

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Sat Nov 16, 2013 9:25 am

Code: Select all

0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
wicd already removed ;)
I've seen that page about broadcom, but I thought b43 would have been the right choice since Elektra works fine with it.
broadcom-sta requires /usr/src/linux-3.10.9. Basically, if I'm getting it right, I need the source of the kernel in use on killX. I grabbed the source, but it's not enough. I've got to build it! It's gonna be a looong weekend.

I'm already in love with this little dude.

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Sat Nov 16, 2013 11:23 am

...an all this now that I (nearly)finished the 'cwm' edition of the Q :)

Well, yes - the broadcom devices are a bit hard to understand... but you see, that's the way a user learns about the intestines of his box. I'm really happy to read not a single word of frustration in your posts :) Good luck!
..gnutella..

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Sat Nov 16, 2013 11:43 am

No frustration whatsoever. With killX and LFS I'm learning so much, I'm already happy. This wireless thing is just another reason to learn something new.

User avatar
GekkoP
Emacs Sancho Panza
Posts: 5878
Joined: Tue Sep 03, 2013 7:05 am

Re: Giving killX some love

Unread post by GekkoP » Sat Nov 16, 2013 2:37 pm

Did it, wireless working in killX!
Here's what I did, in case someone else has a similar issue:

- installed b43-fwcutter and b43-firwmare via sbopkg
- installed wireless-tools via slackpkg
- setup /etc/wpa_supplicant.conf with my wireless connections
- in /etc/rc.d/ added a script called rc.startwlan containing these lines:

Code: Select all

#!/bin/bash
ifconfig lo up
ifconfig wlan0 up
wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf &
dhcpcd wlan0 &
- chmod +x rc.startwlan
- in /etc/rc.d/rc.M added this:

Code: Select all

# Start wlan
if [ -x /etc/rc.d/rc.startwlan ]; then
  . /etc/rc.d/rc.startwlan
fi

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: Giving killX some love

Unread post by machinebacon » Sat Nov 16, 2013 2:47 pm

fucking great! you're a real man now :D

thanks for posting this, it will surely be of use in the future.

Next mission: framebuffer it!
..gnutella..

Post Reply