Giving killX some love
Forum rules
Share your brain ;)
Share your brain ;)
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
^ 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?
I like your zimgur script. Would you shared it sometime, please?
..gnutella..
Re: Giving killX some love
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.
zimgur is in my github repo now.
Connected. Take this REPL, brother, and may it serve you well.
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
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 :)
Thanks for the script, will be of use :)
..gnutella..
Re: Giving killX some love
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.
Re: Giving killX some love
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.
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.
Re: Giving killX some love
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").
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").
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
get an older kernel or compile one yourself, or check htop - maybe gpm is causing high cpu. for me it does.
..gnutella..
Re: Giving killX some love
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.
Re: Giving killX some love
^ lol well, I like trying everything I can before bother you guys ;)
Re: Giving killX some love
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.
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.
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
Thanks :)
I still have LFS going on, but today I'll try to set up killX properly.
I still have LFS going on, but today I'll try to set up killX properly.
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
^ 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..
Re: Giving killX some love
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.
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.
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
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.
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..
Re: Giving killX some love
Code: Select all
0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
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.
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
...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!
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..
Re: Giving killX some love
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.
Re: Giving killX some love
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:
- chmod +x rc.startwlan
- in /etc/rc.d/rc.M added this:
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 &
- 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
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Giving killX some love
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!
thanks for posting this, it will surely be of use in the future.
Next mission: framebuffer it!
..gnutella..