General Linux Chat and Small Questions v. Year of the Linux Desktop! - Hardware & Software

[QUOTE=Levelog;49097454]Looks yummy for folding.[/QUOTE] It would be really cool to have a credit card that doubles as a cancer-curing card.

how would I go about troubleshooting things being incredibly slow? the system works fine, but booting up and logging in takes a lot more time than it should. when I boot up, it takes about 11 seconds to do anything after the "triggering uevents" message. then it discovers my keyboard and mice, complains about them (have a K95 RGB and M65 RGB), then another 20 seconds pass before the rest starts. then once I'm in GDM, it takes about a bloody minute for it to log into Gnome. this hasn't been a problem in the past, I don't understand why it is now. its been like this for a long time though, I don't know if these problems popped up as soon as I installed Arch this time around, or if it popped up somewhere after installing. I also have some minor annoyances after I finally get to my desktop. I have a 144hz screen, so I've had to add a line to my shell to actually set it to 144hz. it's not that bad since I always open a terminal anyway, but it's annoying that it'll black out my screens for a moment since it needs to change the refresh rate. even after that, the only thing which is 144hz is my cursor. for some odd reason I have to open the nvidia control panel for everything else to become 144hz, but this resets my monitors color profile. this means I have to open Gnome settings, turn my color profile off and then back on. now I'm finally able to actually use my computer, and this happens every single time. any idea how I could streamline this?

[QUOTE=PredGD;49098837]how would I go about troubleshooting things being incredibly slow? the system works fine, but booting up and logging in takes a lot more time than it should. when I boot up, it takes about 11 seconds to do anything after the "triggering uevents" message. then it discovers my keyboard and mice, complains about them (have a K95 RGB and M65 RGB), then another 20 seconds pass before the rest starts. then once I'm in GDM, it takes about a bloody minute for it to log into Gnome. this hasn't been a problem in the past, I don't understand why it is now. its been like this for a long time though, I don't know if these problems popped up as soon as I installed Arch this time around, or if it popped up somewhere after installing. I also have some minor annoyances after I finally get to my desktop. I have a 144hz screen, so I've had to add a line to my shell to actually set it to 144hz. it's not that bad since I always open a terminal anyway, but it's annoying that it'll black out my screens for a moment since it needs to change the refresh rate. even after that, the only thing which is 144hz is my cursor. for some odd reason I have to open the nvidia control panel for everything else to become 144hz, but this resets my monitors color profile. this means I have to open Gnome settings, turn my color profile off and then back on. now I'm finally able to actually use my computer, and this happens every single time. any idea how I could streamline this?[/QUOTE] Going through the same shit buddy, it's because gdm is trying to make the hard switch to wayland. To fix GDM taking FOREVER to do anything, uncomment the [code]#WaylandEnable=false[/code] line inside of /etc/gdm/custom.conf. Despite doing this it will still hang after logging in, switching to tty2 somehow gets me into gnome properly after logging in. This even happens on a fresh install, and I'm unsure why still. As for the refresh rates, blame Gnome. I have a 120hz monitor and I literally just run xrandr command manually to get the correct refresh rate. I have NO idea how to fix this permanently for Gnome, I've tried everything. It seems to work fine in any other DE though so if you don't mind ditching Gnome... As for the slow boot times, which file system are you using? I had similar issues when I was using btrfs, but it could also indicate a dying harddrive. You might want to check your S.M.A.R.T. data.

[QUOTE=Naelstrom;49098937]Going through the same shit buddy, it's because gdm is trying to make the hard switch to wayland. To fix GDM taking FOREVER to do anything, uncomment the [code]#WaylandEnable=false[/code] line inside of /etc/gdm/custom.conf. Despite doing this it will still hang after logging in, switching to tty2 somehow gets me into gnome properly after logging in. This even happens on a fresh install, and I'm unsure why still. As for the refresh rates, blame Gnome. I have a 120hz monitor and I literally just run xrandr command manually to get the correct refresh rate. I have NO idea how to fix this permanently for Gnome, I've tried everything. It seems to work fine in any other DE though so if you don't mind ditching Gnome... As for the slow boot times, which file system are you using? I had similar issues when I was using btrfs, but it could also indicate a dying harddrive. You might want to check your S.M.A.R.T. data.[/QUOTE] hopefully that'll fix GDM! yet to try, but I feel optimistic. I've been using xrandr as well, it's a shame Gnome hasn't an in built setting to change these things. I'm pretty sure XFCE and KDE has for example, why doesn't Gnome? shame on them I have two partitions on two drives, with / being on my SSD as ext4 and /home being on my HDD as ext4 as well. Windows boots up really fast as it should, so I don't think anything is dying. I've yet to notice any abnormalities in Windows, these boot issues are only present in Linux. here's my dmesg [url]http://pastebin.com/5es1GTgW[/url] after 2 seconds has passed, it does jack shit for the next 9 seconds for some reason. after that, it does nothing for 10 seconds, then something finally happens but then it delays for yet another 10 seconds before it continues doing what it should. [editline]12th November 2015[/editline] speaking of Wayland, is it anywhere near being usable yet? last time I tried using it, I had plenty of issues.

Looks like you have usb issues. Could you disconnect any USB hubs from your motherboard and see if the issue persists? (Strange how you're getting all the same symptoms as me, I had a malfunc usb hub myself.) The USB hub cables look like this [quote][img]http://cdn.overclock.net/1/16/1655f958_8010826R_USB.jpeg[/img][/quote] plugged into these [quote][img]http://www.motherboards.org/images/reviews/motherboards/2093_p4_13.jpg[/img][/quote]. You shouldn't need them since the motherboard comes with it's own USB hubs(usually on the back), and disconnecting the devices from the hubs is not the same as disconnecting the hubs entirely. [editline]asdf[/editline] We both should make some noise about these bugs (if you've got the same one), they really shouldn't be issues.

[QUOTE=Naelstrom;49099891]Looks like you have usb issues. Could you disconnect any USB hubs from your motherboard and see if the issue persists? (Strange how you're getting all the same symptoms as me, I had a malfunc usb hub myself.) The USB hub cables look like this plugged into these . You shouldn't need them since the motherboard comes with it's own USB hubs(usually on the back), and disconnecting the devices from the hubs is not the same as disconnecting the hubs entirely. [editline]asdf[/editline] We both should make some noise about these bugs (if you've got the same one), they really shouldn't be issues.[/QUOTE] that sounds very likely, I've always experienced issues with my USB2 ports on the front of the case. never really used any of them since I've had issues, so might as well disconnect them. it could be the USB3 one as well as I've managed to bend 2-3 pins and somehow managed to connect it still. it's pretty flakey and keeps connecting and disconnecting, so that could be something as well. I'll definitely try removing the USB2 one first as it was a pain in the ass to connect the USB3 one without snapping off the pins, but if that doesn't help, I'll remove both. will look into it tomorrow

This might sound a bit odd, but does anyone have experience with compiling OpenRC for Debian?

[QUOTE=Samiam22;49081338]R9 270s are indeed affected. You can see benchmarks like [URL="http://www.phoronix.com/scan.php?page=article&item=linux_gpus_high514&num=4"]this one[/URL]. They're usable but lose out to the nVidia ones. Shouldn't be a big deal, though. And the FOSS AMD drivers are decent whereas nouveau is shite.[/QUOTE] The FOSS AMD drivers are ridiculously unstable in my experience, though I can't get the proprietary ones to even start.

In my experience, the FOSS AMD drivers are pretty good, but I only really use Fedora and Debian so I guess I'm biased

[QUOTE=Adam.GameDev;49101611]This might sound a bit odd, but does anyone have experience with compiling OpenRC for Debian?[/QUOTE] isn't it in the repos I'd just check but my only Debian machine seems to have keyboard malfunctions

Yes, but I was hoping to install a more up-to-date version to see what that's like [editline]12th November 2015[/editline] Also I've heard parallel startup is broken on the old versions

[QUOTE=Adam.GameDev;49103100]Yes, but I was hoping to install a more up-to-date version to see what that's like [editline]12th November 2015[/editline] Also I've heard parallel startup is broken on the old versions[/QUOTE] It is, but I thought the maintainer was still maintaining it, so I wasn't aware OpenRC was [b]that[/b] far out of date. This is a Frankenstein of instructions from [url=https://github.com/OpenRC/openrc]OpenRC's git repo[/url] and [url=https://wiki.debian.org/OpenRC]Debian's wiki page[/url], with some Gentoo-experience instructions of my own thrown in: [code]wget "https://github.com/OpenRC/openrc/archive/0.18.3.tar.gz" tar fvxz openrc-0.18.3.tar.gz && cd openrc-0.18.3 export CFLAGS="-O2 -pipe" # or seasoned to taste make install # Service stopper for file in /etc/rc0.d/K*; do s=`basename $(readlink "$file")` ; /etc/init.d/$s stop; done umount -l /all/extra/partitions reboot -f[/code]

Just checked, Debian have finally updated OpenRC to 0.18.3 in Sid. Stretch and Jessie are still at 0.13.1 though [editline]12th November 2015[/editline] Ended up backporting from Sid (Debian has their own patches), but at least now I know what to do in case Debian stops updating OpenRC, so thanks!

[QUOTE=Darkwater124;49080317]Any gamers here using an AMD card? I was wondering about the current state of their Linux drivers. If I were using Windows I'd totally get a R9 380 for my upcoming build but now I'm just not sure.[/QUOTE] They're decent. Games like CS:GO run at 90-120+ FPS for me on a full casual server at 1440p with ultra settings. It used to tank FPS when looking at other players but that's been fixed apparently. More recent games? Shadow of Mordor at 1440p gets around 30FPS-40FPS with low settings and 40FPS-50FPS with lowest. Medium and above runs like total garbage. I don't think this can be purely blamed on the drivers as likely the game hasn't been optimized by the game developers either for AMD.

[QUOTE=Adam.GameDev;49104171]Just checked, Debian have finally updated OpenRC to 0.18.3 in Sid. Stretch and Jessie are still at 0.13.1 though [editline]12th November 2015[/editline] Ended up backporting from Sid (Debian has their own patches), but at least now I know what to do in case Debian stops updating OpenRC, so thanks![/QUOTE] If you're updating from OpenRC to a newer OpenRC version, you don't need to do that complex service stopper command, or really even reboot

[QUOTE=PredGD;49099973]that sounds very likely, I've always experienced issues with my USB2 ports on the front of the case. never really used any of them since I've had issues, so might as well disconnect them. it could be the USB3 one as well as I've managed to bend 2-3 pins and somehow managed to connect it still. it's pretty flakey and keeps connecting and disconnecting, so that could be something as well. I'll definitely try removing the USB2 one first as it was a pain in the ass to connect the USB3 one without snapping off the pins, but if that doesn't help, I'll remove both. will look into it tomorrow[/QUOTE] booted up into Linux today to finally test out GDM and to troubleshoot the booting. booting went incredibly fast as soon as I disconnected both my keyboard and mice which is nice, but it takes ages to finally recognize them when I plug them back in, pretty much as long as it'd normally take to boot with them plugged in anyway. GDM was not fixed either after uncommenting the wayland line and having it at no which sucks.

Found some old documentation I wrote for myself on how to install arch linux on the F205TA. [url]https://github.com/Mechazawa/Arch-Linux-Asus-F205TA/blob/master/README.md[/url] Behold! The most complex way to prepare an arch iso ever! [editline]16th November 2015[/editline] took me ages of trail and error to figure out how that piece of shit worked

Hey, I finally jailbreaked my Lenovo Thinkpad 11e chromebook! running true archlinux with kernel 4.2.5. finally liberated! It required me to remove a "write-protect" screw from the motherboard in order to flash a SeaBios that fits my model. now I'm going through the issues, fixed sound, now The only thing left to do its to make sure it detects an event when I'm closing the lid.

sound just stopped working all of sudden. huh. tried Spotify, can't play any tracks. tried YouTube, it loads the video but never starts it. tried Spotify web player, doesn't start the tracks. tried playing some Binding of Isaac, no sound but works. speaker-test shows no sign of life either. alsa isn't muted, pulseaudio isn't muted either. what to do, how do I troubleshoot this? [editline]18th November 2015[/editline] [url]http://www.alsa-project.org/db/?f=991d7817c7633cf44d90d98d9a77a24ee9d29b21[/url] [editline]18th November 2015[/editline] now it works again. huh

So I decided to give Xubuntu a spin (again) and I seem to have some trouble with the icons. [t]http://imgur.com/ArIIyEgl.png[/t] It doesn't really use some of the icons, and I can't seem to figure out what the problem is [t]http://imgur.com/Kx14EV9l.png[/t] Folders doesn't even show up :suicide:

why do you even bother with nouveau?

running debian with recent hardware is a questionable move, good luck with that.

[QUOTE=Lyoko2;49192990]running debian with recent hardware is a questionable move, good luck with that.[/QUOTE] hahaha because old packages therefore old drivers and it's [i]funny![/i] No. Distro has absolutely nothing to do with hardware recentness, and as long as the drivers exist, in some form or another, it will work exactly the same in Debian as it would in Gentoo, or Fedora, or whatever distro you happen to wank to at night.

[IMG]http://i.imgur.com/phl029C.png[/IMG] Trying out i3wm, I love being able to control stuff without having to unconfortably move my hand to the mouse

[QUOTE=lavacano;49193226]hahaha because old packages therefore old drivers and it's [i]funny![/i] No. Distro has absolutely nothing to do with hardware recentness, and as long as the drivers exist, in some form or another, it will work exactly the same in Debian as it would in Gentoo, or Fedora, or whatever distro you happen to wank to at night.[/QUOTE] Wouldn't Debian's kernel need the drivers though?

[QUOTE=Adam.GameDev;49200469]Wouldn't Debian's kernel need the drivers though?[/QUOTE] Debian would probably backport the drivers as far as kernel 2.x if it was technically feasible and they still had a supported version running a kernel that old they have some goddamn dedication to their "old but tested" packages

So i've been rolling with gnome 3 for the past few days and it's pretty darn great. It looks nice and third-party extensions are neat (and fill in the gaps that the gnome team left). There's just one thing though... [img]http://i.imgur.com/urRfW94.png[/img] This thing is a cpu eater like nothing else, but the thing is, what is it doing? Everything is fine and dandy, I open up the application view or the overview and the cpu just spikes like nuts. Is it phantom cpu usage or something? I even tried to turn animations off and it still does it (as per recommendations from other people with this problem). It's not like it's hurting my computing experience (I didn't even notice it until I glanced at system monitor), just wondering because it's kind of strange.

[QUOTE=thatbooisaspy;49212634]So i've been rolling with gnome 3 for the past few days and it's pretty darn great. It looks nice and third-party extensions are neat (and fill in the gaps that the gnome team left). There's just one thing though... This thing is a cpu eater like nothing else, but the thing is, what is it doing? Everything is fine and dandy, I open up the application view or the overview and the cpu just spikes like nuts. Is it phantom cpu usage or something? I even tried to turn animations off and it still does it (as per recommendations from other people with this problem). It's not like it's hurting my computing experience (I didn't even notice it until I glanced at system monitor), just wondering because it's kind of strange.[/QUOTE] GNOME just has a lot of clutter inside of it. Some parts with Vala, the whole GObject mumbo jumbo, [URL=https://git.gnome.org/browse/gnome-shell/tree/src/shell-js.cpp]JavaScript[/URL], [URl=https://git.gnome.org/browse/gnome-shell-sass/tree/]Sass stylesheets[/URL], you name it. All that absctraction is almost as bad as enterprise-grade software. As for "what is it doing?", [URL=https://git.gnome.org/browse/]check in the core suite[/url].

Just finished my first gentoo install on my laptop running LXDE. Pretty impressed at how smoothly it went, although I probably screwed up on the networking setup since I had to write my own rc.d script to get it working, firefox was a pain in the ass to compile as well, it would randomly fail so I had to enable the keepwork feature and emerge -r until it completed.

I had a bit of fun when doing a Gentoo reinstall before the start of my second year of Uni, we each had a personal harddrive that we docked into a series of computers, so that we could keep our own environments. Decided to see what would happen if I set up all the USE flags and then did "emerge -jav <all of X and KDE>". (Basically, download and compile all of the X and KDE packages, with an unlimited amount of jobs allowed at the same time) When I dropped by later that day and looked at it, it had a load average of about ~250 Was lucky to be part of the welcoming committee so I could have the computer room for myself in the beginning week, otherwise I would've had to do it in a reasonable way.