Whoa, this took a freakin' long time to fix! Here was my problem: VLC wouldn't play encrypted DVDs, which was really aggravating. After installing a whole slew of codecs, I think it's only right to finally share what ended up working. First, I should mention it -still- doesn't work in VLC. In fact, the only way I got it to work was to use a different player altogether, gxine. So here is the work around, which I got from this link.
1.) Add the following lines to /etc/apt/sources.list
##Medibuntu-Ubuntu 7.10 gutsy gibbon
##Please report any bug on https://launchpad.net/products/medibuntu/+bugs
deb http://medibuntu.sos-sts.com/repo/ gutsy free non-free
deb-src http://medibuntu.sos-sts.com/repo/ gutsy free non-free
2.) from the command line, run: sudo apt-get upgrade
3.) sudo apt-get install libdvdread3 libdvdcss2 gstreamer xine-ui libxine1-ffmpeg gxine regionset
4.) Make sure your region is set using regionset (set region to 1) -- I suspect most people won't need to do this
5.) from the command line, run: sudo /usr/share/doc/libdvdread3/examples/install-css.sh, or simply: sudo /usr/share/doc/libdvdread3/install-css.sh
6.) Go to System --> Preferences --> Removable Drives and Media
7.) Click on the "multimedia" tab. Under "Video DVD discs" Click "play video DVD discs when inserted" and enter the following for the command:
gxine -S dvd:/
Pop in a DVD and it should work!
---------------------------------
UPDATE: ok... so it -does- also work with VLC now. Win?
UPDATE 2: It works with xine as well :-) Sick. Ok, I declare update this from "bandaid"ed, to fixed!
Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts
Sunday, April 06, 2008
Saturday, November 10, 2007
Ubuntu 7.10 - Gutsy Gibbon (VPN running)
Back in linux, I follow the link and download the file. After unzipping the tar.bz2 file, I cd in and run ./vpn_install. Magic happens. Next, to start the thing. In the future, I hopefully don't have to do this, since it should be done automatically:
sudo /etc/init.d/vpnclient_init start
Ok, next, I need profiles. Before, when love was on the side of vpnc, I would have to enter the gateway info, and two passwords. This was doable, and ok. Now I need profiles. With a touch of chagrin, I realize that this probably the program that the help desk wanted me to run all along, though the tar file I downloaded was different. Going back to the RPI helpdesk site, I download the necessary .pcf files and put them in /etc/opt/cisco-vpnclient/Profiles/
The following command is then used:
sudo vpnclient connect RPI_External_VPN
Magic happens: user names and passwords are entered, information is exchanged. Sparkles and rainbows shoot out of my terminal. And suddenly..!
Negotiating security policies.
Securing communication channel.
Your VPN connection is secure.
To check, I try to connect to my server. No problems! Hooray! VPN now works!
Ugh. It's been fun, I think. I haven't checked RPI Wireless yet, but something tells me it will work (before it didn't). So overall, a productive and good use of time.
I -am- hungry. Maybe food is in order? That's a good idea. Food, and a hot shower.
Till next time...
-Suzanne
sudo /etc/init.d/vpnclient_init start
Ok, next, I need profiles. Before, when love was on the side of vpnc, I would have to enter the gateway info, and two passwords. This was doable, and ok. Now I need profiles. With a touch of chagrin, I realize that this probably the program that the help desk wanted me to run all along, though the tar file I downloaded was different. Going back to the RPI helpdesk site, I download the necessary .pcf files and put them in /etc/opt/cisco-vpnclient/Profiles/
The following command is then used:
sudo vpnclient connect RPI_External_VPN
Magic happens: user names and passwords are entered, information is exchanged. Sparkles and rainbows shoot out of my terminal. And suddenly..!
Negotiating security policies.
Securing communication channel.
Your VPN connection is secure.
To check, I try to connect to my server. No problems! Hooray! VPN now works!
Ugh. It's been fun, I think. I haven't checked RPI Wireless yet, but something tells me it will work (before it didn't). So overall, a productive and good use of time.
I -am- hungry. Maybe food is in order? That's a good idea. Food, and a hot shower.
Till next time...
-Suzanne
Ubuntu 7.10 - Gutsy Gibbon (Fixing VPN)
Now in Windows, I test out my Cisco external VPN connection. After successfully being able to connect to my server (which is now behind the firewall -- another rant), I knew there wasn't anything wrong with External VPN. So one of two things must have happened.
By some hidden magic, External VPN no longer supports vpnc, or by some other hidden magic, vpnc changed somehow from Ubuntu 7.04, to 7.10, in an unproductive manner for me.
I head over the help-desk site and see the package that they have for linux. I shudder I -really- don't want to deal with their shit if I can get things working on my own. Back to ubuntu forums. Sure enough, other people seemed to be having a similar problem.
I now have the following instructions:
You can find the client here:
http://linux-support.hiwi.rz.uni-kon...1.0640.tar.bz2
Extract the file. Make sure, that you have installed the kernel headers and then run
sudo ./vpn_install
Link
h'okay, then, let's see what we get. Reboot into linux.
By some hidden magic, External VPN no longer supports vpnc, or by some other hidden magic, vpnc changed somehow from Ubuntu 7.04, to 7.10, in an unproductive manner for me.
I head over the help-desk site and see the package that they have for linux. I shudder I -really- don't want to deal with their shit if I can get things working on my own. Back to ubuntu forums. Sure enough, other people seemed to be having a similar problem.
I now have the following instructions:
You can find the client here:
http://linux-support.hiwi.rz.uni-kon...1.0640.tar.bz2
Extract the file. Make sure, that you have installed the kernel headers and then run
sudo ./vpn_install
Link
h'okay, then, let's see what we get. Reboot into linux.
Ubuntu 7.10 - Gutsy Gibbon
So I developed a nasty head cold last night, and as of this morning, am still feeling pretty terrible. I think among the things necessary for a cure are food and fluids, neither of which I've had since my meager bowl of oatmeal last night.
Because I wasn't feeling well, I played on my DS, but eventually got bored. So I decided to upgrade my current system, which ran Ubuntu Fiesty 7.4 to Ubuntu Gutsy 7.10. Flipped open system upgrade, and told it to upgrade to 7.10.
I immediately began having doubts. Usually, when a new OS comes out, there are bugs here and there, and I winced remembering my wireless adventure dealing with my network stuff. Things were working perfectly now, after all.. why change things?
To test how well the upgrade will actually upgrade my system, rather than downgrade it, I authorized the go ahead.
The upgrade was relatively painless; it took about an hour to download the upgrades, and another hour to install all the updates, which was pretty reasonable, especially since I don't have the best of wireless connections here at the apartment. So, I restarted the system to see what it all looked like.
Things were ... mostly the same. Gaim had disappeared, since now Pidgin is exclusively supported. I added the Pidgin Icon to the panel, rearranged it some, and my panel looked as good as normal, save for this weird purple pigeon icon being where my simple, yet elegant yellow man icon used to be. Ah well, I'll get over it. The biggest change was that wireless was no longer working. At all.
SHIT, I thought. This could be for several reasons. 1.) Something different is going on that it was in Fiesty 2.) Something different is going on and it's going on worse because I TOLD ubuntu during the upgrade process to keep the modified blacklist file. SHIT, I thought, shit, shit, shit shit.. Worst of all, at that point in time, I had forgotten that the blacklist file was called "blacklist", so I didn't know where to look.
Rebooted into windows. Came to my blog, saw the notes I made last time about blacklisting goodness. Went back into linux. Located and went into this file:
/etc/modeprob.d/blacklist
After looking at the tail of the list, sure enough, my original changes were there. shit, I thought. So it' s no longer hostap that's the problem... wait, but what if hostap has control, and orinoco is the trouble? A few quick changes to the blacklist file yielded the tail of blacklist to look like this:
#buggy network-manager causes ornico to fight with it for wireless card
#blacklist hostap
#blacklist hostap_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci
blacklist orinoco
blacklist orinoco_pci
With my fingers crossed, I restarted the system. Ubuntu came back up, and lo and behold! Wireless was working! Hooray! Scanning is re-enabled, and things looked like it was full of win. I was pleased to see that vpnc was part of the default install, and that all my previous settings were saved. Let's see if I can connect to the external VPN. A button click and two passwords yielded:
VPN Connect Failure
Could not start the VPN connection 'External VPN' due to a connection error.
The VPN login failed because the VPN program could not connect to the VPN server.
Shit, I thought. Not good. I checked configuration file. No problems seem to be there, since indeed, it was my previous settings. I was able to connect via external VPN no problem since I last checked, which was two days ago. Could something actually be wrong with External VPN connection at RPI? or is it VPNc? Let's check.
System reboot into Windows.
Because I wasn't feeling well, I played on my DS, but eventually got bored. So I decided to upgrade my current system, which ran Ubuntu Fiesty 7.4 to Ubuntu Gutsy 7.10. Flipped open system upgrade, and told it to upgrade to 7.10.
I immediately began having doubts. Usually, when a new OS comes out, there are bugs here and there, and I winced remembering my wireless adventure dealing with my network stuff. Things were working perfectly now, after all.. why change things?
To test how well the upgrade will actually upgrade my system, rather than downgrade it, I authorized the go ahead.
The upgrade was relatively painless; it took about an hour to download the upgrades, and another hour to install all the updates, which was pretty reasonable, especially since I don't have the best of wireless connections here at the apartment. So, I restarted the system to see what it all looked like.
Things were ... mostly the same. Gaim had disappeared, since now Pidgin is exclusively supported. I added the Pidgin Icon to the panel, rearranged it some, and my panel looked as good as normal, save for this weird purple pigeon icon being where my simple, yet elegant yellow man icon used to be. Ah well, I'll get over it. The biggest change was that wireless was no longer working. At all.
SHIT, I thought. This could be for several reasons. 1.) Something different is going on that it was in Fiesty 2.) Something different is going on and it's going on worse because I TOLD ubuntu during the upgrade process to keep the modified blacklist file. SHIT, I thought, shit, shit, shit shit.. Worst of all, at that point in time, I had forgotten that the blacklist file was called "blacklist", so I didn't know where to look.
Rebooted into windows. Came to my blog, saw the notes I made last time about blacklisting goodness. Went back into linux. Located and went into this file:
/etc/modeprob.d/blacklist
After looking at the tail of the list, sure enough, my original changes were there. shit, I thought. So it' s no longer hostap that's the problem... wait, but what if hostap has control, and orinoco is the trouble? A few quick changes to the blacklist file yielded the tail of blacklist to look like this:
#buggy network-manager causes ornico to fight with it for wireless card
#blacklist hostap
#blacklist hostap_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci
blacklist orinoco
blacklist orinoco_pci
With my fingers crossed, I restarted the system. Ubuntu came back up, and lo and behold! Wireless was working! Hooray! Scanning is re-enabled, and things looked like it was full of win. I was pleased to see that vpnc was part of the default install, and that all my previous settings were saved. Let's see if I can connect to the external VPN. A button click and two passwords yielded:
VPN Connect Failure
Could not start the VPN connection 'External VPN' due to a connection error.
The VPN login failed because the VPN program could not connect to the VPN server.
Shit, I thought. Not good. I checked configuration file. No problems seem to be there, since indeed, it was my previous settings. I was able to connect via external VPN no problem since I last checked, which was two days ago. Could something actually be wrong with External VPN connection at RPI? or is it VPNc? Let's check.
System reboot into Windows.
Wednesday, August 08, 2007
Wireless Adventure - Part IV (Wireless in Linux)
As I write this, I'm logged into my Ubuntu partition on my laptop. We have total and complete success!
This is great. Not only can I scan for wireless networks now, I can also connect! I'm so excited.
Lessons learned:
network-manager: friend
orinoco: friend
hostap: THE DEVIL
Ubuntu Fiesty Fawn: Completely f-ing awesome.
Now, to sit back and enjoy my intrawebs on my linux partition! How shall I celebrate?
I know. Watch as many Flight of the Conchords episodes as I can!
Then some Planet Earth! ^-^
I am completely pleased with myself.
Wireless Adventure: Success!
This is great. Not only can I scan for wireless networks now, I can also connect! I'm so excited.
Lessons learned:
network-manager: friend
orinoco: friend
hostap: THE DEVIL
Ubuntu Fiesty Fawn: Completely f-ing awesome.
Now, to sit back and enjoy my intrawebs on my linux partition! How shall I celebrate?
I know. Watch as many Flight of the Conchords episodes as I can!
Then some Planet Earth! ^-^
I am completely pleased with myself.
Wireless Adventure: Success!
Wireless Adventure - Part III (Blacklisting hostap)
So blacklisting Orinoco had some positive effects. Now, I can scan for wireless networks (whoopee!) As you can imagine, this was very exciting. I thought I had finally got it to work.
Unfortunately no.
I'm now thinking about blacklisting hostap instead of Orinoco:
my etc/modprobe.d/blacklist file should now read like this:
blacklist prism2_pci
blacklist hostap_pci
blacklist hostap
Let's see how this works!
More update goodness soon.
Unfortunately no.
I'm now thinking about blacklisting hostap instead of Orinoco:
my etc/modprobe.d/blacklist file should now read like this:
blacklist prism2_pci
blacklist hostap_pci
blacklist hostap
Let's see how this works!
More update goodness soon.
Wireless Adventure - Part II (Blacklisting Orinoco)
More poking around the internets. Lucking I found this.
To quote:
The problem is that the hostap and orinoco kernel modules are competing for control of the card. This is mentioned as a likely problem on NetworkManager site:
(http://live.gnome.org/NetworkManagerHardware)
hostap: "Supports unencrypted, WEP, WPA, and WPA2 networks. Be aware that if you have both this driver and the 'orinoco' driver installed, they may fight for control of the wireless card and render it inoperable to NetworkManager. You should either disable one of these drivers, or ensure that only one driver is able to control the card."
Thank you, Brett!
To summarize the instructions:
1. Check to make sure I'm dealing with the right network card: I entered the following command in bash:
:~ lspci | grep Network
I got:
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
HA! It matched. Yes! Next, for adding some blacklisting marks to
/etc/modprobe.d/blacklist:
blacklist orinoco
blacklist orinoco_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci
Last step, reboot!
Completing this process took less than two minutes (even less time than it took me to install WICD), and it was relatively straightforward.
I still don't know if it will work yet. I have to go home and see. But I have my fingers crossed! Results later. Hopefully, this should do it!
To quote:
The problem is that the hostap and orinoco kernel modules are competing for control of the card. This is mentioned as a likely problem on NetworkManager site:
(http://live.gnome.org/NetworkManagerHardware)
hostap: "Supports unencrypted, WEP, WPA, and WPA2 networks. Be aware that if you have both this driver and the 'orinoco' driver installed, they may fight for control of the wireless card and render it inoperable to NetworkManager. You should either disable one of these drivers, or ensure that only one driver is able to control the card."
Thank you, Brett!
To summarize the instructions:
1. Check to make sure I'm dealing with the right network card: I entered the following command in bash:
:~ lspci | grep Network
I got:
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
HA! It matched. Yes! Next, for adding some blacklisting marks to
/etc/modprobe.d/blacklist:
blacklist orinoco
blacklist orinoco_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci
Last step, reboot!
Completing this process took less than two minutes (even less time than it took me to install WICD), and it was relatively straightforward.
I still don't know if it will work yet. I have to go home and see. But I have my fingers crossed! Results later. Hopefully, this should do it!
Wireless Adventure - Part I (WICD)
I looked for suggestions. The first one was WICD. It looked great. A lot of people seemed to be having the same problem, and WICD seemed to just fix it very quickly. Also, the Digg reviewers were treating it like the second coming of Christ: "GREAT interface! network-manager BLOWS! ALL my wirless problems were FIXED when I started using WICD! AND it improved my sex life! FIVE+++ StArS!" Sheesh.
Installation was breeze. I was liking this already! Now came the fun part: testing it out. The interface was lot larger than network-managers. One thing I didn't like about it right away, is that it didn't automatically connect to my WIRED network, which was annoying. Furthermore it required me to create a profile for each IP (for -wired- connections). I didn't like this at all. Since I connect to the internet all over the place, the last thing I wanted was to have a bunch of "profiles" cluttering up the interface, most of which I will probably never use again. Of course, I won't delete any of them in the off-chance that I -do- use them again(and who wants to enter all that information again?). Too aggravating. The kicker was that it wasn't detecting the wireless network present.
That would have been okay. network-manager wouldn't automatically detect wireless networks. I just had to enter them in manually. But, as it would turn out, in WICD, there is no way for me to manually enter a wireless network it didn't detect (they had a "hidden network" box, which allowed you to enter a ESSID, and no encryption key, which wasn't satisfactory.) Maybe I should have given WICD more time. Maybe I should have poked around more. Maybe I was dumb and wasn't looking at the interface closely enough. Could the solution have still been there?
Whatever. I uninstalled WICD and reinstalled network-manager. Back to square one!
Installation was breeze. I was liking this already! Now came the fun part: testing it out. The interface was lot larger than network-managers. One thing I didn't like about it right away, is that it didn't automatically connect to my WIRED network, which was annoying. Furthermore it required me to create a profile for each IP (for -wired- connections). I didn't like this at all. Since I connect to the internet all over the place, the last thing I wanted was to have a bunch of "profiles" cluttering up the interface, most of which I will probably never use again. Of course, I won't delete any of them in the off-chance that I -do- use them again(and who wants to enter all that information again?). Too aggravating. The kicker was that it wasn't detecting the wireless network present.
That would have been okay. network-manager wouldn't automatically detect wireless networks. I just had to enter them in manually. But, as it would turn out, in WICD, there is no way for me to manually enter a wireless network it didn't detect (they had a "hidden network" box, which allowed you to enter a ESSID, and no encryption key, which wasn't satisfactory.) Maybe I should have given WICD more time. Maybe I should have poked around more. Maybe I was dumb and wasn't looking at the interface closely enough. Could the solution have still been there?
Whatever. I uninstalled WICD and reinstalled network-manager. Back to square one!
Wireless Adventure - Introduction
So my IBM ThinkPad T30, Phoenix, got a makeover earlier this summer. Due to my general laziness and strange attachment to Ubuntu Breezy, I didn't update to Dapper. When Feisty came out, I found out that I could no longer update my system, period. Shit.
Among other things, this meant that I couldn't do an automatic update to Dapper, and then from there, into Feisty. So, I wiped my partition (after backing up my data) and did a clean install of Ubuntu Feisty Fawn 7.04. That, plus giving Phoenix a new fan and an additional 512 MB stick of RAM, she seemed ready to rock the world.
I really like Feisty Fawn. It's sleeker, cleaner, and it got rid of some minor annoyances I had with Breezy. Perfect set up, I thought.
Then it turned out that my wireless card wouldn't work.
I was mystified. In Breezy, my wireless card worked fine. There was a bug that prevented me from scanning for wireless networks, but as long as I knew the SSID and/or password of the network I was trying to connect to, things worked fine.
Did something go horribly wrong? Did I do something wrong? Why is my wireless card not being recognized? I rebooted into Windows. Maybe it's the network that's at fault?
In XP (where I can scan for wireless networks fine), I located the wireless network I wanted to connect to. I entered the WEP key. Everything worked fine. So nope, nothing wrong with the card, nothing wrong with the network.
Doing some poking around the internets revealed that this is a known bug with network-manager, which, of course, made things so much easier for me. But how to fix the bug?
This multipart (hopefully not too long) series of posts in this blog will chronicle my wireless adventures. Will end when either I give up, or my wireless works in Ubuntu. And, I don't want to "rollback" (if that's even possible for me, considering I did a clean install of Feisty) to Dapper Drake. Let's see who wins!
Among other things, this meant that I couldn't do an automatic update to Dapper, and then from there, into Feisty. So, I wiped my partition (after backing up my data) and did a clean install of Ubuntu Feisty Fawn 7.04. That, plus giving Phoenix a new fan and an additional 512 MB stick of RAM, she seemed ready to rock the world.
I really like Feisty Fawn. It's sleeker, cleaner, and it got rid of some minor annoyances I had with Breezy. Perfect set up, I thought.
Then it turned out that my wireless card wouldn't work.
I was mystified. In Breezy, my wireless card worked fine. There was a bug that prevented me from scanning for wireless networks, but as long as I knew the SSID and/or password of the network I was trying to connect to, things worked fine.
Did something go horribly wrong? Did I do something wrong? Why is my wireless card not being recognized? I rebooted into Windows. Maybe it's the network that's at fault?
In XP (where I can scan for wireless networks fine), I located the wireless network I wanted to connect to. I entered the WEP key. Everything worked fine. So nope, nothing wrong with the card, nothing wrong with the network.
Doing some poking around the internets revealed that this is a known bug with network-manager, which, of course, made things so much easier for me. But how to fix the bug?
This multipart (hopefully not too long) series of posts in this blog will chronicle my wireless adventures. Will end when either I give up, or my wireless works in Ubuntu. And, I don't want to "rollback" (if that's even possible for me, considering I did a clean install of Feisty) to Dapper Drake. Let's see who wins!
Subscribe to:
Posts (Atom)