Forums/Version 2/Beta testing support area
Just put on latest updates and Driver and Linux locks up with in 2 to 5 minutes
Cmp828
asked this on Jan 15 11:10
Hello,
This is strange for me. January 11th I saw updates and applied them for the latest Beta. I installed the update by the command listed in the e-mail e-mail to use. Rebooted and let things go, was late that night. I checked a few days later and the server was locked up. Yesterday 1-14-2012 the system after a reboot was up long enough for me to do a apt / update check and it saw updates and applied them. I let synaptic package manager update. Rebooted. System starts and I can get logged in. But 2 to 5 minutes after logging in or just being turned on and running (not logged into it) the system locks up. The display freezes. Can't log in, no mouse, total Freeze up of the OS / Computer. Everything was fine Up to 1-11-2012 or what ever the exact date was when I saw the e-mail to update the driver to the current. I assume, had to be something in the update since nothing else was done to the box, and I was able to remote log into the server via web and with NoMachine's Free NX remote client application to do the updates. The Camera server was running fine up to that point before the update.
System has a Asus p5e-vmDO motherboard with a Intel Core 2 Quad CPU q8400lga775 2.66ghz running on Ubuntu 10.04LTS
8 gigs ram with OS on 2 tb drive and recording set to record on a 500 gig drive.
Looks like I updated after Jan 9th for the driver and then on the 14th for the server of 2 beta 9.2
I am going to reload Ubuntu, might go to the 11.04 or 11.10 will have to see how far out they are supported and then reload everything and see.
Otherwise the entire time and all Beta testing updates have for the most part gone very well and have been very pleased with how the beta testing has been going. Besides running the DVR / Blue Cherry, I also run my web server from this machine and both have run just fine side by side, main reason why I went from dual core to quad core and put the Recordings on another drive and 8gig ram. The system runs fine on the dual core with 2 gigs ram for the 16 port card with 14 cameras.
Well off to reload Ubuntu and Blue Cherry after I back up key config files from the drive. I athink I might lean to Ubuntu 11.04 or 11.10.
Chad
Comments
This is a known issue with the 2.4.0 driver. This driver should fix it:
wget http://lizard.bluecherry.net/~curt/tmp/solo6010-dkms_2.4.1-1_all.deb ; sudo dpkg -i solo6010-dkms_2.4.1-1_all.deb
I am still backing files up from that hard drive in the DVR system. I did have Synaptic set to keep the deb packages after it downloads and installs. I checked the var\cache\apt location and it had the solo6010 file in there dated 1-9. 30% left of the backup of my web server directory left to go. then I can put drive back in server and boot up and see if I can run your commands, else at this point, I suppose I could just rerun the install of Linux and reload Bluecherry fresh. Yep I was able to add the driver on or after the 9th and then Saturday applied the server update to the system and then noticed after a spell it locked up. Thank you for your quick reply. Still have to install the last two cameras to have the full 16 cams going. I average 10 hour days at work doing the I.T. stuff there and then come home and don't want to look at mine, so its usually the weekends when I am free to dive into my own computer things. Will keep you posted.
Chad
Anything but neat and clean, update not working. Loading APT to to see if Ican get the driver installed with APT. If I install clean from scratch will I assume it will install all the correct fiels and latest driver? I have already removecd all of bluecherry to start over. Just trying to get the driver loaded first, then go back reloading bluecherry. Looks like the lockup issue gone for the moment with solo and bluecherry removed. Screens when I tried to install the driver.
schad@cpu2:~$ sudo dpkg -i solo6010-dkms_2.4.1-1_all.deb
[sudo] password for chad:
dpkg-deb: unexpected end of file in version number in solo6010-dkms_2.4.1-1_all.deb
dpkg: error processing solo6010-dkms_2.4.1-1_all.deb (--install):
subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
solo6010-dkms_2.4.1-1_all.deb
chad@cpu2:~$ sudo dpkg -i solo6010-dkms_2.4.1-1_all.deb
dpkg-deb: unexpected end of file in version number in solo6010-dkms_2.4.1-1_all.deb
dpkg: error processing solo6010-dkms_2.4.1-1_all.deb (--install):
subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
solo6010-dkms_2.4.1-1_all.deb
chad@cpu2:~$ sudo apt-get update ; sudo apt-get install solo6010-dkms
Ign http://ubuntu.bluecherrydvr.com lucid Release.gpg
Ign http://ubuntu.bluecherrydvr.com/ lucid/main Translation-en_US
Hit http://ubuntu.bluecherrydvr.com lucid Release
Hit http://security.ubuntu.com lucid-security Release.gpg
Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-en_US
Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-en_US
Hit http://software.virtualmin.com virtualmin-lucid Release.gpg
Hit http://us.archive.ubuntu.com lucid Release.gpg
Ign http://us.archive.ubuntu.com/ubuntu/ lucid/main Translation-en_US
Ign http://us.archive.ubuntu.com/ubuntu/ lucid/restricted Translation-en_US
Ign http://ubuntu.bluecherrydvr.com lucid/main Packages
Get:1 http://deb.opera.com stable Release.gpg [189B]
Ign http://deb.opera.com/opera/ stable/non-free Translation-en_US
Ign http://security.ubuntu.com/ubuntu/ lucid-security/universe Translation-en_US
Ign http://security.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-en_US
Hit http://security.ubuntu.com lucid-security Release
Ign http://software.virtualmin.com/gpl/ubuntu/ virtualmin-lucid/main Translation-en_US
Ign http://ubuntu.bluecherrydvr.com lucid/main Packages
Ign http://us.archive.ubuntu.com/ubuntu/ lucid/universe Translation-en_US
Ign http://us.archive.ubuntu.com/ubuntu/ lucid/multiverse Translation-en_US
Hit http://us.archive.ubuntu.com lucid-updates Release.gpg
Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Translation-en_US
Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/restricted Translation-en_US
Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe Translation-en_US
Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/multiverse Translation-en_US
Hit http://us.archive.ubuntu.com lucid Release
Hit http://ubuntu.bluecherrydvr.com lucid/main Packages
Get:2 http://deb.opera.com stable Release [633B]
Ign http://deb.opera.com stable Release
Hit http://software.virtualmin.com virtualmin-universal Release.gpg
Hit http://us.archive.ubuntu.com lucid-updates Release
Hit http://security.ubuntu.com lucid-security/main Packages
Hit http://archive.canonical.com lucid Release.gpg
Ign http://archive.canonical.com/ubuntu/ lucid/partner Translation-en_US
Ign http://deb.opera.com stable/non-free Packages
Ign http://software.virtualmin.com/gpl/ubuntu/ virtualmin-universal/main Translation-en_US
Hit http://us.archive.ubuntu.com lucid/main Packages
Hit http://us.archive.ubuntu.com lucid/restricted Packages
Hit http://us.archive.ubuntu.com lucid/main Sources
Hit http://us.archive.ubuntu.com lucid/restricted Sources
Hit http://us.archive.ubuntu.com lucid/universe Packages
Hit http://us.archive.ubuntu.com lucid/universe Sources
Hit http://security.ubuntu.com lucid-security/restricted Packages
Hit http://security.ubuntu.com lucid-security/main Sources
Hit http://security.ubuntu.com lucid-security/restricted Sources
Hit http://security.ubuntu.com lucid-security/universe Packages
Hit http://security.ubuntu.com lucid-security/universe Sources
Hit http://security.ubuntu.com lucid-security/multiverse Packages
Hit http://archive.canonical.com lucid Release
Hit http://software.virtualmin.com virtualmin-lucid Release
Ign http://deb.opera.com stable/non-free Packages
Hit http://us.archive.ubuntu.com lucid/multiverse Packages
Hit http://security.ubuntu.com lucid-security/multiverse Sources
Hit http://archive.canonical.com lucid/partner Packages
Hit http://software.virtualmin.com virtualmin-universal Release
Hit http://deb.opera.com stable/non-free Packages
Hit http://us.archive.ubuntu.com lucid/multiverse Sources
Hit http://us.archive.ubuntu.com lucid-updates/main Packages
Hit http://us.archive.ubuntu.com lucid-updates/restricted Packages
Hit http://us.archive.ubuntu.com lucid-updates/main Sources
Hit http://us.archive.ubuntu.com lucid-updates/restricted Sources
Hit http://us.archive.ubuntu.com lucid-updates/universe Packages
Hit http://us.archive.ubuntu.com lucid-updates/universe Sources
Hit http://us.archive.ubuntu.com lucid-updates/multiverse Packages
Hit http://us.archive.ubuntu.com lucid-updates/multiverse Sources
Hit http://software.virtualmin.com virtualmin-lucid/main Packages
Hit http://software.virtualmin.com virtualmin-universal/main Packages
Fetched 190B in 1s (151B/s)
Reading package lists... Done
W: GPG error: http://deb.opera.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AAFF4A5B336064B5
Reading package lists... Done
Building dependency tree
Reading state information... Done
solo6010-dkms is already the newest version.
solo6010-dkms set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
chad@cpu2:~$
2nd try:
chad@cpu2:~$ wget http://lizard.bluecherry.net/~curt/tmp/solo6010-dkms_2.4.1-1_all.deb ; sudo dpkg -i solo6010-dkms_2.4.1-1_all.deb
--2012-01-15 16:59:13-- http://lizard.bluecherry.net/~curt/tmp/solo6010-dkms_2.4.1-1_all.deb
Resolving lizard.bluecherry.net... 184.107.191.98
Connecting to lizard.bluecherry.net|184.107.191.98|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58296 (57K) [application/x-debian-package]
Saving to: `solo6010-dkms_2.4.1-1_all.deb.1'
100%[======================================>] 58,296 177K/s in 0.3s
2012-01-15 16:59:14 (177 KB/s) - `solo6010-dkms_2.4.1-1_all.deb.1' saved [58296/58296]
[sudo] password for chad:
dpkg-deb: unexpected end of file in version number in solo6010-dkms_2.4.1-1_all.deb
dpkg: error processing solo6010-dkms_2.4.1-1_all.deb (--install):
subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
solo6010-dkms_2.4.1-1_all.deb
chad@cpu2:~$
Note: in the first pass when it said it had the latest solo version, that was the 2.4.0 driver and not the 2.4.1-1. When synaptic would run it listed and only showed the 2.4.0 loaded.
Run this:
md5sum solo6010-dkms_2.4.1-1_all.deb
It should show:
1b5d0bf7919d400a50363506a0eb8fb7 solo6010-dkms_2.4.1-1_all.deb
If it doesn't, remove solo6010-dkms_2.4.1-1_all.deb and download it again
Question, when will the bluecherry install be fixed to incluse the solo6010 2.4.1-1_all driver? I had removed everything and installed bluecherry and I see it put the 2.4.0 version on. Not able to update the driver to 2.4.1-1, so far the system has not locked up after 20 minutes, but if 2.4.1-1 is the latest driver we should be using, how soon will the bluecherry install have it included in its normal install process from a fresh first time install?
I rather have bleucherry removed cleanly and just start all over installing from a fresh current install and if need can wait a few days to restore my system. Still running on Ubuntu 10.04. Don't want to relaod Ubuntu at this time.
Chad
You never have to reload Ubuntu, that is a waste, neither is completing removing the bluecherry package.
The solo6010 driver will never be part of the Bluecherry install. It's not required for customers using IP cameras.
Hello
I Ran the command from the e-mail and the md5sum did not match. Was able to get installed fine now. Thank you. I had tried downloading a few times and saw it just appended a 2 and 3 and made new files so I was always still trying to use the problem file. I am sure the copy 2 or 3 was fine. Go figure.
Yes I don't normally want to reload Ubuntu. My DVR / BlueCherry recordings are not critical and I can remove and install Bluecherry and its not an issue for me at my home. I will need to get some I.P. cameras to play with. I like the idea of the I.P. cameras and not have to home run each camera feed. Thank you for all the help. Don't have the $$ right now to prebuy the 16 port / 16 camera license early, but as soon as I have the funds for it, I will be buying it. Been very happy with the Beta testing and the v 2.0. I think you have a fine product.
Chad
The below process resolved the issue, delete the file and pulled in a new fresh file and it worked.
md5sum solo6010-dkms_2.4.1-1_all.deb
It should show:
1b5d0bf7919d400a50363506a0eb8fb7 solo6010-dkms_2.4.1-1_all.deb
If it doesn't, remove solo6010-dkms_2.4.1-1_all.deb and download it again
Just updated to beta 9.2 and got a kernel panic too. Testing 2.4.1-1 driver now.
If the problem is in the driver, why did it crash after I install 9.2?
I took a picture of the panic message if you need it.
Cheers,
Melby,
There shouldn't be anything in 9.2 that would caused the driver to lockup. 2.4.0 of the driver will cause random machines to hard lock, and was fixed in the 2.4.1 testing release.
Thanks
We had lots of trouble here with the 2.4.1 driver; we had installed it Monday in hopes of resolving the hard lock issues which we were also experiencing with the 2.4.0 driver.
After having to come back in to the office late in the evening for the third time this week to deal with a non-responsive server, we rolled back to the 2.3.7 driver, which had served us well. Currently it seems to be working alright with the 9.2 server beta; at least, it got us through last night and into mid-morning without issues.
Eric,
Are you sure that you installed 2.4.1, or did you install 2.4.0? The changes that caused the hard locking in 2.4.0 were reverted back to what they were from 2.3.7 and put into the 2.4.1 pre-release package that I linked on the first response.
If you did install 2.4.1, then we'll need access to that computer to figure out what the problem is.
We installed 2.4.0 early last week, on the 10th. Prior to this, our system had been running fairly stable for some time. Afterwards we had issues with the server locking up and becoming non-responsive, even to ssh and ping requests; we also had issues with the client displaying flickering video/color flashes/camera images showing under the wrong port name.
I then installed the 9.2 server update on Friday the 13th. Continued having troubles through the weekend.
While troubleshooting those on Monday morning, I came across this thread and your comment on the 15th to cmp828 above. Installed the 2.4.1 driver then.Things seemed okay for a couple of hours, then the same symptoms started recurring.
After rolling back to 2.3.7 driver last night, we've had our first stretch of 12 hours of uninterrupted recording and viewing all week.
Eric,
When you run 2.4.1 does it print a kernel panic when it locks up? If so, a picture of that would be very useful.
We've been running the server headless, so I'm not certain.