UP 2014.01.15 [PRODUCTION] [DONE]

Important informations about SolydXK including releases notes, forum rules and other anouncements
User avatar
Orbmiser
Posts: 829
Joined: 24 Aug 2013 22:58
Location: Portland,Oregon

Re: UP 2014.01.15 [PRODUCTION]

Postby Orbmiser » 19 Jan 2014 21:13

grizzler wrote:Message #50 in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725978 seems to suggest this as a possible solution:
Thanks for the link. Kernel polling can also be enabled with this in /etc/rc.local:

echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs
It's also mentioned in message #35 in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877

Perhaps there's a way to add this to the iso?
Confirmed added the line "echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs" to the rc.local script before the exit 0 at the end
mkdir -p /dev/cgroup/cpu
mount -t cgroup cgroup /dev/cgroup/cpu -o cpu
mkdir -m 0777 /dev/cgroup/cpu/user
echo "/usr/local/sbin/cgroup_clean" > /dev/cgroup/cpu/release_agent
echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs

exit 0
Rebooted and DVD drive & SD cards working normally.
.
Portfolio
http://500px.com/Orbmiser
Flickr
http://www.flickr.com/photos/orb9220/

SolydK - Kernel 3.16-2-amd64 - KDE 4.14.1 Update Pack: 2014.10.15

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: UP 2014.01.15 [PRODUCTION]

Postby ScottQuier » 19 Jan 2014 21:22

stelios wrote:How about running the command

Code: Select all

udisks --enumerate
This will start the old daemon. If it works, you can make it run automatically at startup.
That seems to work. I ran it in a terminal window, opened the DVD drive, inserted the disk and closed the drive. The disk is now ready for mounting.
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

User avatar
stelios
Posts: 128
Joined: 28 Feb 2013 21:31
Location: Athens

Re: UP 2014.01.15 [PRODUCTION]

Postby stelios » 19 Jan 2014 21:27

Although i do not have the problem, i tried it to see if it would cause a problem at startup. It did not, but it had an unexpected positive result: startup time was significantly reduced.. Which was really surprising.

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: UP 2014.01.15 [PRODUCTION]

Postby ScottQuier » 19 Jan 2014 21:39

stelios wrote:Although i do not have the problem, i tried it to see if it would cause a problem at startup. It did not, but it had an unexpected positive result: startup time was significantly reduced.. Which was really surprising.
Tried which? And how?
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

User avatar
stelios
Posts: 128
Joined: 28 Feb 2013 21:31
Location: Athens

Re: UP 2014.01.15 [PRODUCTION]

Postby stelios » 19 Jan 2014 21:49

ScottQuier wrote:
stelios wrote:Although i do not have the problem, i tried it to see if it would cause a problem at startup. It did not, but it had an unexpected positive result: startup time was significantly reduced.. Which was really surprising.
Tried which? And how?
The best way to start a daemon is through the init.d system, but just to test it i simply went to system settings-> startup and shutdown and added the command there (don;t forget to check under "properties-permissions" the executable box when you add it)

Image

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: UP 2014.01.15 [PRODUCTION]

Postby ScottQuier » 19 Jan 2014 22:28

stelios wrote:
ScottQuier wrote:
stelios wrote:Although i do not have the problem, i tried it to see if it would cause a problem at startup. It did not, but it had an unexpected positive result: startup time was significantly reduced.. Which was really surprising.
Tried which? And how?
The best way to start a daemon is through the init.d system, but just to test it i simply went to system settings-> startup and shutdown and added the command there (don;t forget to check under "properties-permissions" the executable box when you add it)
Doing it via system settings worked for me as well. But, now I have one more thing to research -- init.d system. Such fun!

Thanks!
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

User avatar
Arjen Balfoort
Site Admin
Posts: 9309
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP 2014.01.15 [PRODUCTION]

Postby Arjen Balfoort » 19 Jan 2014 22:41

I like Orbmiser's solution.
However, does it affect both SolydX, and SolydK, and both 32-bit, and 64-bit versions?


SolydXK needs you!
Development | Testing | Translations

User avatar
wyrdoak
Posts: 113
Joined: 07 Jan 2014 21:25

Re: UP 2014.01.15 [PRODUCTION]

Postby wyrdoak » 19 Jan 2014 23:00

Schoelje wrote:I like Orbmiser's solution.
However, does it affect both SolydX, and SolydK, and both 32-bit, and 64-bit versions?
It's working in SolydX 32bit here. :D Tried music,data and video, CD's and DVDs both store bought and homemade. ;)

Not pinning gvfs anymore ether.

BTW: It's the only addition I've been able to make to rc.local script so far that hasn't knocked out my SD. card.

Acer Aspire One AO532h; CPU Atom n450 1.66Gh: 2GB RAM, duel boot with Win7: SolydK32

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: UP 2014.01.15 [PRODUCTION]

Postby ScottQuier » 19 Jan 2014 23:58

Schoelje wrote:I like Orbmiser's solution.
However, does it affect both SolydX, and SolydK, and both 32-bit, and 64-bit versions?
I can only talk to SolydK 64-bit, but it works like a champ.
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

User avatar
Orbmiser
Posts: 829
Joined: 24 Aug 2013 22:58
Location: Portland,Oregon

Re: UP 2014.01.15 [PRODUCTION]

Postby Orbmiser » 20 Jan 2014 02:00

Schoelje wrote:I like Orbmiser's solution.
However, does it affect both SolydX, and SolydK, and both 32-bit, and 64-bit versions?
My guess is Yes as seen this issue discussed from mate,xfce,KDE,Gnome and think it's a udisks & udisks2 issue coupled with whether the kernel has polling enabled.

https://www.google.com/search?as_qdr=y& ... poll_msecs
To permanently enable polling (survives a reboot), add the following command to your /etc/rc.local file (anywhere before the 'exit' line in that file):

echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs

Any number between 2000 and 5000 (milliseconds) should be reasonable - the higher 5000 means poll every 5 seconds, which is less overhead but a little slower.

OR you can pass this option to the kernel boot command line in grub:

block.events_dfl_poll_msecs=2000
Portfolio
http://500px.com/Orbmiser
Flickr
http://www.flickr.com/photos/orb9220/

SolydK - Kernel 3.16-2-amd64 - KDE 4.14.1 Update Pack: 2014.10.15

User avatar
grizzler
Posts: 2175
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP 2014.01.15 [PRODUCTION]

Postby grizzler » 20 Jan 2014 07:00

Schoelje wrote:I like Orbmiser's solution.
However, does it affect both SolydX, and SolydK, and both 32-bit, and 64-bit versions?
After I mentioned it yesterday, I tested it on my 64-bit SolydX. Works like a charm.
Frank

SolydX EE 64 - tracking Debian Testing

j.st.
Posts: 10
Joined: 20 Jan 2014 07:42
Location: Germany

Re: UP 2014.01.15 [PRODUCTION]

Postby j.st. » 20 Jan 2014 07:59

zerozero wrote:
ScoobyDan wrote:Hi,

I don't know if this should be posted here, or as a separate thread...

Since installing the UP 2014.01.15 yesterday, I am unable to mount any SD/MMC cards inserted into my card reader, unless they are inserted before the computer is powered on. My external (USB) HDD mounts no problem, but a SD card inserted into a USB adapter will not be seen by the system - they do not appear in the Device Notifier tray icon or anywhere within the file system (such as under '/dev'). If I insert the card before booting the computer, it can be accessed until it is removed - upon re-inserting it, the card is not seen.

The only issue I had during the UP process was the '/var/cache/apt/archives/libc6_2.17-97_amd64.deb' error mentioned previously, easily corrected by 'sudo apt-get install -f' followed by restarting the UP process.

Any ideas?

Daniel
SolydK 64-bit
UP 2014.01.15
Hi Daniel
we had for some time reports that automounting of optical media was no working as it was supposed but mass-storage devices were;
somehow now it got worst, they are both MIA.
Ideally we should after the "dust" settles a bit more in this UP migration start looking into that.
here are some links (there's more in the forum and outside, it's just a starting point)
http://forums.solydxk.nl/viewtopic.php?f=9&t=1227
http://forums.solydxk.nl/viewtopic.php? ... hilit=udev
Hello,

I have the same issue after installing the UP 2014.01.15. After reading here in the forum and searching around I have found this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877.

The described solution in rc.local solved my problems. I am using Linux for a long time but I am not a expert but I think the described Ubuntu solution (with a new rule) is the more elegant solution. I will try it in the next days, but in my opinion an expert should take a look -> this could be a permanent solution.

Sorry for my English, I'm out of practice.

Jens
Linux user since 1998 -> Suse -> Kubuntu -> Linux Mint KDE and now SolydK


User avatar
Arjen Balfoort
Site Admin
Posts: 9309
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP 2014.01.15 [PRODUCTION]

Postby Arjen Balfoort » 20 Jan 2014 08:15

Hi Jens, and welcome to our forum!

I'm building the new ISO's right now, with the extra line in rc.local
You can follow the testing of the ISO's here: http://forums.solydxk.nl/viewtopic.php? ... 13&p=24890


SolydXK needs you!
Development | Testing | Translations

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: UP 2014.01.15 [PRODUCTION]

Postby zerozero » 20 Jan 2014 10:10

in my particular situation none of the solutions presented above (lshw, udisks --enumerate, the rc.local rule) solves the issue :(

the usb-sticks are good (tested in another system and promptly recognized) but they have the same behavior in 3 different Solyd systems (in 2 different hardware): they are seen by the bios, also in gparted/partition manager but that's about it; can't see them anywhere else.
USB-HDD work as expected.

didn't test optical media but i remember that it was a problem as well.
bliss of ignorance

Deleted User 580

Re: UP 2014.01.15 [PRODUCTION]

Postby Deleted User 580 » 20 Jan 2014 10:26

The rc.local solution works for me as well.

eidnch
Posts: 21
Joined: 12 Nov 2013 09:38

Re: UP 2014.01.15 [PRODUCTION]

Postby eidnch » 24 Jan 2014 13:02

For this time the upgrade didn't work with the update-manager because the here already mentioned dependency problem with libc6:i386 and libgcc1:i386

I solved the problem with: sudo apt-get -f install

The reason why i post here is, that the post-upgrade like descriped in the news:

sudo apt-get install –reinstall nvidia-kernel-dkms

don't work for every system and that should be considerd for the next upgrade. Because the reinstall of the kernel modules installs on my system the wrong driver and brake the system. For older cards the driver 304 is needed and not 319, which is installed by reinstall the kernel modules. For now the only solution i have to work with is the sgfxi script but i don't know if the next upgrade with the update-manager will work now, because the script installs the driver not from the repository. What i can do now?

User avatar
smitty1
Posts: 244
Joined: 23 Jun 2013 13:50
Location: Pittsburgh, PA USA

Re: UP 2014.01.15 [PRODUCTION]

Postby smitty1 » 24 Jan 2014 15:42

Schoelje wrote:I like Orbmiser's solution.
However, does it affect both SolydX, and SolydK, and both 32-bit, and 64-bit versions?
I tried it in both SolydX and SolydK, each 64 bit, and it works.
FWIW the original /etc/rc.local file in SolydX was empty, but for comments. Obviously the difference did not anything That I do regularly, just thought it was odd.

No Good Deed Goes Unpunished

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: UP 2014.01.15 [PRODUCTION]

Postby zerozero » 24 Jan 2014 23:14

zerozero wrote:in my particular situation none of the solutions presented above (lshw, udisks --enumerate, the rc.local rule) solves the issue :(

the usb-sticks are good (tested in another system and promptly recognized) but they have the same behavior in 3 different Solyd systems (in 2 different hardware): they are seen by the bios, also in gparted/partition manager but that's about it; can't see them anywhere else.
USB-HDD work as expected.

didn't test optical media but i remember that it was a problem as well.
the rc.local fix actually works here as well;
the problem is/was that usb-sticks formatted with ImageWriter

Code: Select all

Disk /dev/sdc: 4009 MB, 4009754624 bytes
64 heads, 32 sectors/track, 3824 cylinders, total 7831552 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x04843793

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           0     2467839     1233920   17  Hidden HPFS/NTFS

Disk /dev/sdc1: 1263 MB, 1263534080 bytes
64 heads, 32 sectors/track, 1205 cylinders, total 2467840 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x04843793

     Device Boot      Start         End      Blocks   Id  System
/dev/sdc1p1   *           0     2467839     1233920   17  Hidden HPFS/NTFS
aren't mounted. if i format it with partition-manager to any kind of F-S it mounts automatically
[still doesn't explain why the same usb-stick is mounted in arch]
bliss of ignorance

j.st.
Posts: 10
Joined: 20 Jan 2014 07:42
Location: Germany

Re: UP 2014.01.15 [PRODUCTION]

Postby j.st. » 27 Jan 2014 10:14

Hi,

I had the same NVIDIA problem, every time there is a new driver update. I think it is NVIDIAs fault, because the new drivers don´t support older cards.

My solution was to put every NVIDA relevant package on hold, so they won´t get future updates. It was a little bit tricky to find the right packages but now it works.

Maybe time to buy new hardware :)

Jens
eidnch wrote:For this time the upgrade didn't work with the update-manager because the here already mentioned dependency problem with libc6:i386 and libgcc1:i386

I solved the problem with: sudo apt-get -f install

The reason why i post here is, that the post-upgrade like descriped in the news:

sudo apt-get install –reinstall nvidia-kernel-dkms

don't work for every system and that should be considerd for the next upgrade. Because the reinstall of the kernel modules installs on my system the wrong driver and brake the system. For older cards the driver 304 is needed and not 319, which is installed by reinstall the kernel modules. For now the only solution i have to work with is the sgfxi script but i don't know if the next upgrade with the update-manager will work now, because the script installs the driver not from the repository. What i can do now?
Linux user since 1998 -> Suse -> Kubuntu -> Linux Mint KDE and now SolydK


eidnch
Posts: 21
Joined: 12 Nov 2013 09:38

Re: UP 2014.01.15 [PRODUCTION]

Postby eidnch » 27 Jan 2014 10:57

Thankyou for your suggestion. Which packages you hold back and how you made this? With preferences?


Return to “News & Anouncements”

Who is online

Users browsing this forum: No registered users and 3 guests