Re: [gentoo-user] mplayer is blue!
On 7/10/05, Michael Sullivan [EMAIL PROTECTED] wrote: My gmplayer screen (using the X11/Xv video driver (which is the only driver that provides adequate full-screen performance)) is showing blue. The movie's sound comes through, but no picture - just that blue screen. I seem to remember someone had this same problem several months ago, but I cannot seem to find the thread in the archives at gmane.org. Can anyone help me? -- gentoo-user@gentoo.org mailing list I had the exact same problem. I read somewhere about using the USE flags mmx and 3dnow. I think I tried just the mmx and it solved the problem for me. mmx is for Pentium type processors. Best regards! Danny -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Baselayout update blasted my wireless networking
On 6/13/05, Richard Fish [EMAIL PROTECTED] wrote: Danny Luker wrote: Hi all, The other night I did an emerge sync; emerge world -vu and got a new and improved version of baselayout. I screwed up and let etc-update clobber all my config files (stupid I know ;() ... anyway, I've recovered from it except I can't get wireless working. It all was so simple before. Even doing it manually was simple but I can't get it to connect (associate) with my access points. Before all this I could do it manually by: # modprobe ath_pci // using the madwifi drivers on my Thinkpad T40 # ifconfig ath0 192.168.1.53 netmask 255.255.255.0 up # route add default gw 192.168.1.1 ath0 Well, nothing in the new baselayout should have prevented your ability to bring things up manually. The only thing I can think of that you might be missing is an iwconfig ath0 essid 'any' command. For bringing things up automatically, the following lines in /etc/conf.d/net should work: modules_ath0=( ifconfig iwconfig ) config_ath0=( 192.168.1.53 netmask 255.255.255.0 ) routes_ath0=( default via 192.168.1.1 ) If you need encryption, you will also need to configure /etc/conf.d/wireless appropriately. Take a look at /etc/conf.d/net.example and wireless.example. If this doesn't help, please post your /etc/conf.d/net and wireless files. And also exactly what happens when you try to bring up the interface manually. -Richard -- gentoo-user@gentoo.org mailing list Thanks Richard, I have since made progress in the area of manually bringing up wireless. I discovered, after much experimentation, that I can get my interface to play well by giving it the following: iwconfig ap off and then proceding with ifconfig and route as normal. Still can't get it to do it automatically. And, like you, I don't understand why the base layout change would cause me to have to issue the above command when I never had to in the past. So, after putting the text in /etc/conf.d/net you suggested I get the same results. I tried adding the ap off in the /etc/conf.d/wireless iwconfig_ath0 variable ... didn't work. Tried a little preup() function to issue the iwconfig ap off command ... didn't work ... well at least I can do it manually now ;) As for what it does ... * Starting ath0 * Loading networking modules for ath0 * modules: iwconfig essidnet iptunnel ifconfig dhcpcd apipa * iwconfig provides wireless * ifconfig provides interface * dhcpcd provides dhcp * Running preup function iwconfig ath0 ap off * Configuring wireless network for ath0 * Connecting to any (WEP Disabled) ... [ !! ] * Failed to configure wireless for ath0[ !! ] /var/log/messages gets an entry ... Jun 13 04:27:49 localhost rc-scripts: Failed to configure wireless for ath0 and nothing else very interesting happens ... I wish there were more info ;) Maybe I just do know where to look .. ;( I've attached the net and wireless config files. Thank you for taking time to look at this ... really has me scratching my head. Danny Luker net Description: Binary data wireless Description: Binary data
Re: [gentoo-user] Baselayout update blasted my wireless networking
On 6/13/05, Glenn Enright [EMAIL PROTECTED] wrote: On Mon, 13 Jun 2005 13:17, Danny Luker wrote: Hi all, The other night I did an emerge sync; emerge world -vu and got a new and improved version of baselayout. I screwed up and let etc-update clobber all my config files (stupid I know ;() ... anyway, I've recovered from it except I can't get wireless working. snip Prob not useful, but when I upgraded I got error messages on reboot from having my net.eth0 in the 'boot' runlevel, rather than 'default'. Not sure why the change, but moving it to 'default' made everything work again and error messgaes went away. Is this helpful? -- For every complex problem, there is a solution that is simple, neat, and wrong. -- H. L. Mencken Thanks for the info ... I checked and my net.lo is in boot. net.ath0 is in default. I think this is correct but I could be mistaken. Thank you. Danny Luker -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Baselayout update blasted my wireless networking
On 6/13/05, Richard Fish [EMAIL PROTECTED] wrote: Danny Luker wrote: Thanks Richard, I have since made progress in the area of manually bringing up wireless. I discovered, after much experimentation, that I can get my interface to play well by giving it the following: iwconfig ap off That's an 'odd' command to have to issue...how is your wireless network setup? Do you actually have an access point, or do you have another PC providing the network access? The first is generally known as managed mode, the other is ad-hoc mode. iwconfig ath0 ap off * Configuring wireless network for ath0 * Connecting to any (WEP Disabled) ... Well, if you don't have an access point, I see the problem. At the point the 'Connecting to any...' message appears, the network scripts do the equivalent of iwconfig ath0 essid any, which undoes your ap off command. If you are using ad-hock mode, you can try to set the following in /etc/conf.d/wireless: essid_ath0=off mode_ath0=ad-hoc The essid..off setting might cause an error. It isn't officially supported, although it should be a valid option to iwconfig for an essid. If it causes an error, just comment it out. -Richard -- gentoo-user@gentoo.org mailing list I never had to issue that command before and I do have a access point. Pretty standard Netgear 802.11b setup. No encryption, MAC access restriction, channel 1 ... nothing out of the normal and nothing has been changed on the AP. I have tried ad-hoc ... just out of curiosity ... no luck. When I issue the iwconfig ap off command the system connects in managed mode. I will try the ad-hoc parameters you suggested. Thanks, Danny -- gentoo-user@gentoo.org mailing list
