Re: [arch-general] howto properly disable sound device pulse/alsa?
On 07/10/2011 07:44 PM, Matthew Monaco wrote: I think since Gnome 3 / pulseaudio, I've had an annoying system beep when shutting down. The pcspkr module is not loaded. Are you blacklisting this module through the old syntax in rc.conf? The configuration for blacklisting modules changed not too long ago (although not terribly recently, either, so sorry if you were already aware of this). http://www.archlinux.org/news/changes-to-module-blacklisting/
Re: [arch-general] iptables not working well?
On Sun, Jul 10, 2011 at 6:25 PM, Damjan Georgievski wrote: > Your config looks ok, but to double check, paste the output of: > iptables -L -nv > iptables -t nat -L -nv > to see the exact situation. > > >> OK, on machines at the internal side of my LAN, I can ping everywhere. >> But I can not use the browser with all addresses, for example I can't >> get to www.archlinux.org through frirefox or midori, neither >> www.debian.org. >> >> Weird thing www.google.com, and some other sites can be reached >> through firefox on machines inside the LAN. > > What's the error you are getting. Are you ping-ing by name or by an IP > address. > Have you tried ping-ing with different packet sizes? No error at all, just that the browser gets waiting to connect, and nevers does it. Pinging is always fine with no specification of packet size. > > on your gateway machine run tcpdump on both the LAN and ppp0 interface > and see if the packets go through. I might try that. What I'll do for now is enable new connections on both sides, since the ones coming from outside are not accepted (but that's the way that sounds common sense to me, and that has been working on my debian box for quiet a while)... Again, no error, just the browser not getting anywhere for some sites. Some others work as google and gmail... > > > -- > damjan > Thanks, -- Javier.
Re: [arch-general] howto properly disable sound device pulse/alsa?
On 07/10/2011 08:50 PM, jesse jaara wrote: Just enable the alsa daemon in rc.conf so that sound levels get reloaded on boot according to what they were at shutdown time. ^^ Yeah, I know about this, but is there a way to just put it in a config file without the alsa-utils package?
Re: [arch-general] howto properly disable sound device pulse/alsa?
Just enable the alsa daemon in rc.conf so that sound levels get reloaded on boot according to what they were at shutdown time. ^^
[arch-general] howto properly disable sound device pulse/alsa?
I think since Gnome 3 / pulseaudio, I've had an annoying system beep when shutting down. The pcspkr module is not loaded. I've found that I have the following device: $ dmesg | grep Beep [ 10.594164] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input7 And that the following command will disable the beep: $ amixer -c0 set Beep 0% mute How should I go about making this persistent? I think avoiding that device would be best, can it be done by adding (or disabling) some udev config? Or, can I somehow make the 0% mute persistant in asound.conf? Thanks
Re: [arch-general] iptables not working well?
Your config looks ok, but to double check, paste the output of: iptables -L -nv iptables -t nat -L -nv to see the exact situation. > OK, on machines at the internal side of my LAN, I can ping everywhere. > But I can not use the browser with all addresses, for example I can't > get to www.archlinux.org through frirefox or midori, neither > www.debian.org. > > Weird thing www.google.com, and some other sites can be reached > through firefox on machines inside the LAN. What's the error you are getting. Are you ping-ing by name or by an IP address. Have you tried ping-ing with different packet sizes? on your gateway machine run tcpdump on both the LAN and ppp0 interface and see if the packets go through. -- damjan
Re: [arch-general] iptables not working well?
>> If you have a static IP address on your ethernet card, you probably want to >> use SNAT rather than MASQUERADE. >> >> Also, I find it odd that you are using MASQUERADE on traffic TO the ppp0 >> interface. Usually, ou MASQUERADE traffic FROM the ppp0 address. You might >> try >> "-i" instead of "-o" in that rule and see if it makes a difference > > It's workin like I showed on a debian box. But I'll try of course. I don't see the previous message in my mailbox, but… he is wrong. The correct way is -o ppp0, you want to MASQUERADE everything that goes out of your internet facing interface. -- damjan
Re: [arch-general] iptables not working well?
On Sun, Jul 10, 2011 at 5:02 PM, Dr. Robert Marmorstein wrote: > If you have a static IP address on your ethernet card, you probably want to > use SNAT rather than MASQUERADE. > > Also, I find it odd that you are using MASQUERADE on traffic TO the ppp0 > interface. Usually, ou MASQUERADE traffic FROM the ppp0 address. You might > try > "-i" instead of "-o" in that rule and see if it makes a difference It's workin like I showed on a debian box. But I'll try of course. > > Your state rules also look a little odd to me. On your INPUT chain, you are > accepting traffic that is established or related. But you only accept new > connections if they are not from ppp0. I think I would delete the "! -i ppp0" > from that line unless you have a very good reason for it to be there. ppp0 is my connection to the external world (ISP through PPPoE), so the idea is not to accept new connections from the outside. That seemed logical to me. And has been working on the debian box for quiet a while. However I'll remove conditional acceptance, just plain accept new connections both from inside as from outside. > > Furthermore, there should be an equivalent line that alow the FORWARD chain to > accept NEW connections, but that seems to be missing. > > Since you don't seem to really have any real security rules in your firewall > anyway, I suggest something like this: > > iptables -P INPUT ACCEPT > iptables -P FORWARD ACCEPT > iptables -P OUTPUT ACCEPT > iptables -F > iptales -t nat -F > iptales -t mangle -F > iptales -X > > iptables -A INPUT -i lo -j ACCEPT > iptables -A INPUT -m state --state ESTABLISHED, RELATED -j ACCEPT > iptables -A FORWARD -m state --state ESTABLISHED, RELATED -j ACCEPT > iptables -A INPUT -i ppp0 -m state --state NEW -j ACCEPT > iptables -A FORWARD -ippp0 -m state --state NEW -j ACCEPT > iptables -t nat -A POSTROUTING -i ppp0 -o eth0 -j MASQUERADE > iptables -A INPUT -j REJECT > iptables -A FORWARD -j REJECT > > Of course, since I'm not on your system, I can't test these. But I think this > is more or less what you're trying to do. I'll experiment a bit with your settings, I hope you're right, :-) Notice that even though my setting look a bit dated, they're still working for me on an old debian box (which I'm trying to replace)... > > In terms of security stuff, I strongly recommend you think about adding some > limit matches -- at least for SSH and HTTP ports if you have them open. Yes, I haven't set a firewall, just a transparent gateway, I mean a plane router between my ISP and my internal LAN. So far I don't have any service, like web or mail, so it hadn't been much of a constrain, but I can learn how to do things and implement them. Perhaps you can share later on more on your suggestions for more security, :-) > > Hope this helps, Yeap, I'll try, and then will let you and the list know... > > Robert Thanks a lot, -- Javier.
Re: [arch-general] Nvidia?? (About to do pacman -Syu but:)
It would appear that on Jul 10, Vic Demuzere did say: > Maybe I should have explained that more. > > As you can see on the arch wiki [1], you either use "nvidia" OR > "nvidia-173xx and nvidia-96xx". That means that if you're currently > using "nvidia", you won't have any problems with updating. > > [1] https://wiki.archlinux.org/index.php/NVIDIA#Installing THANKS! now to get around to that pacman -Syu -- |^^^ ^^^ Guess I just didn't know. |Joseph (the Wordy) Philbrook |^ J(tWdy)P | ___
Re: [arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
On 07/10/2011 03:40 PM, jesse jaara wrote: 2011/7/10 Nicolás Adamo On 07/10/2011 02:18 PM, Nicolás Adamo wrote: First of all, Thanks for so much reply! nomodeset was already in menu.lst wat wasn't there is fglrx in modules array @t rc.conf , but on other desktop machine it isn't necessary. The wiki page doesn't ask for it when using the repo [catalyst] Either way I'll try adding it and I'll tell you guys later how it worked out. (I don't have the netbook now) I'll also post another pastebin with the log output suggested. 2011/7/10 jesse jaara: 10.7.2011 11.35 "Bogdan Ionuț" kirjoitti: On Sun, Jul 10, 2011 at 11:33, jesse jaara wrote: nokms not nomodeset!? Oh sorry I did mean nomodeset. No wonder nokms looked like it was way too short. Also I assume you have loaded the fglrx module. Try to run just bare 'Xorg> ./x.log' so you get atleast somekind of an output saved for inspection. Adding fglrx to modules array didn't make a change. Running Xorg makes no visible output , so x.log is an empty file, even running it as super user. I'm lost again... O_o Does dmesg have something it it about fglrx Jesse here's the output of dmesg |grep fglr: http://pastebin.archlinux.fr/433095 and here's the complete output: http://pastebin.archlinux.fr/433096 Thanks
Re: [arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
2011/7/10 Nicolás Adamo > On 07/10/2011 02:18 PM, Nicolás Adamo wrote: > >> First of all, Thanks for so much reply! >> nomodeset was already in menu.lst >> wat wasn't there is fglrx in modules array @t rc.conf , but on other >> desktop machine it isn't necessary. The wiki page doesn't ask for it >> when using the repo [catalyst] >> Either way I'll try adding it and I'll tell you guys later how it >> worked out. (I don't have the netbook now) >> I'll also post another pastebin with the log output suggested. >> >> 2011/7/10 jesse jaara: >> >>> 10.7.2011 11.35 "Bogdan Ionuț" kirjoitti: >>> On Sun, Jul 10, 2011 at 11:33, jesse jaara wrote: nokms > not nomodeset!? >>> Oh sorry I did mean nomodeset. No wonder nokms looked like it was way too >>> short. Also I assume you have loaded the fglrx module. >>> >>> Try to run just bare 'Xorg> ./x.log' so you get atleast somekind of an >>> output saved for inspection. >>> >>> Adding fglrx to modules array didn't make a change. > Running Xorg makes no visible output , so x.log is an empty file, even > running it as super user. > > I'm lost again... > O_o Does dmesg have something it it about fglrx -- (\_ /) copy the bunny to your profile (0.o ) to help him achieve world domination. (> <) come join the dark side. /_|_\ (we have cookies.)
Re: [arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
On 07/10/2011 02:18 PM, Nicolás Adamo wrote: First of all, Thanks for so much reply! nomodeset was already in menu.lst wat wasn't there is fglrx in modules array @t rc.conf , but on other desktop machine it isn't necessary. The wiki page doesn't ask for it when using the repo [catalyst] Either way I'll try adding it and I'll tell you guys later how it worked out. (I don't have the netbook now) I'll also post another pastebin with the log output suggested. 2011/7/10 jesse jaara: 10.7.2011 11.35 "Bogdan Ionuț" kirjoitti: On Sun, Jul 10, 2011 at 11:33, jesse jaara wrote: nokms not nomodeset!? Oh sorry I did mean nomodeset. No wonder nokms looked like it was way too short. Also I assume you have loaded the fglrx module. Try to run just bare 'Xorg> ./x.log' so you get atleast somekind of an output saved for inspection. Adding fglrx to modules array didn't make a change. Running Xorg makes no visible output , so x.log is an empty file, even running it as super user. I'm lost again...
Re: [arch-general] Nvidia?? (About to do pacman -Syu but:)
On 07/10/2011 07:25 PM, Vic Demuzere wrote: > On 07/10/2011 07:22 PM, Joe(theWordy)Philbrook wrote: >> according to pacman -Q nvidia I got: >> nvidia 270.41.19-1 >> >> Should I worry about it? >> That is should I find out how to prevent pacman >> from messing with the video driver, or does the "270.41.19-1" >> mean the above will have no effect on my nvidia driver? >> > > You're using the nvidia package, and that is still in the repository. > > http://www.archlinux.org/packages/extra/x86_64/nvidia/ > Maybe I should have explained that more. As you can see on the arch wiki [1], you either use "nvidia" OR "nvidia-173xx and nvidia-96xx". That means that if you're currently using "nvidia", you won't have any problems with updating. [1] https://wiki.archlinux.org/index.php/NVIDIA#Installing -- vic.demuzere.be :: v...@demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Nvidia?? (About to do pacman -Syu but:)
On 07/10/2011 07:22 PM, Joe(theWordy)Philbrook wrote: > according to pacman -Q nvidia I got: > nvidia 270.41.19-1 > > Should I worry about it? That is should I find out how to prevent pacman > from messing with the video driver, or does the "270.41.19-1" mean the > above will have no effect on my nvidia driver? > You're using the nvidia package, and that is still in the repository. http://www.archlinux.org/packages/extra/x86_64/nvidia/ -- vic.demuzere.be :: v...@demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features. signature.asc Description: OpenPGP digital signature
[arch-general] Nvidia?? (About to do pacman -Syu but:)
In preparation for a pacman -Syu I peeked at the "main page" and read: > The nvidia-173xx and nvidia-96xx driver packages have been removed from > our repositories as they are incompatible with newer xorg servers. This > can only be fixed by an upstream update, which has not happened yet. > > For most video cards, the best alternative should be xf86-video-nouveau Since I know for a fact that my integrated Nvidia GeForce 6150 LE is very incompatible with the nouveau driver I'm suddenly concerned... according to pacman -Q nvidia I got: nvidia 270.41.19-1 Should I worry about it? That is should I find out how to prevent pacman from messing with the video driver, or does the "270.41.19-1" mean the above will have no effect on my nvidia driver? Thanks -- | ~^~ ~^~ |Joe (theWordy) Philbrook | ^J(tWdy)P |\___/ <>
Re: [arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
First of all, Thanks for so much reply! nomodeset was already in menu.lst wat wasn't there is fglrx in modules array @t rc.conf , but on other desktop machine it isn't necessary. The wiki page doesn't ask for it when using the repo [catalyst] Either way I'll try adding it and I'll tell you guys later how it worked out. (I don't have the netbook now) I'll also post another pastebin with the log output suggested. 2011/7/10 jesse jaara : > 10.7.2011 11.35 "Bogdan Ionuț" kirjoitti: >> >> On Sun, Jul 10, 2011 at 11:33, jesse jaara wrote: >> >> > nokms >> >> not nomodeset!? > > Oh sorry I did mean nomodeset. No wonder nokms looked like it was way too > short. Also I assume you have loaded the fglrx module. > > Try to run just bare 'Xorg > ./x.log' so you get atleast somekind of an > output saved for inspection. >
[arch-general] iptables not working well?
Hi, I've configured a 2-nics gateway (one internal nic and an external usb nic hooked to the adsl modem). I configured iptables as I'm used to do: ++ iptables-restore < /etc/iptables/empty.rules iptables -P INPUT ACCEPT iptables -P FORWARD ACCEPT iptables -P OUTPUT ACCEPT iptables -F iptables -t nat -F iptables -t mangle -F iptables -X iptables -A INPUT -i lo -j ACCEPT iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A INPUT -m state --state NEW ! -i ppp0 -j ACCEPT iptables -A FORWARD -m state --state ESTABLISHED,RELATED -i ppp0 -o eth0 -j ACCEPT iptables -A FORWARD -i eth0 -o ppp0 -j ACCEPT iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE iptables -A FORWARD -i ppp0 -o ppp0 -j REJECT /etc/rc.d/iptables save /etc/rc.d/iptables restart ++ Notice that I have IP forwarding enabled through: ++ % 'grep' forward /etc/sysctl.conf net.ipv4.ip_forward=1 net.ipv6.conf.all.forwarding=1 ++ And also through: ++ % 'grep' FORWARD /etc/conf.d/iptables IPTABLES_FORWARD=1 ++ But I can confirm by: +++ % cat /proc/sys/net/ipv4/ip_forward 1 +++ This is based upon: http://www.debian-administration.org/articles/23 And it's working on a debian box. I remember some time back it also worked on a arch box, only thing I was not using pppd directly but wvdial instead... OK, on machines at the internal side of my LAN, I can ping everywhere. But I can not use the browser with all addresses, for example I can't get to www.archlinux.org through frirefox or midori, neither www.debian.org. Weird thing www.google.com, and some other sites can be reached through firefox on machines inside the LAN. When I try accessing those sites on the gateway (not the machines inside the LAN) of course I have no problem. I checked /etc/resolv.con, and it's OK, besides ping has clear access everywhere. I have no clue what's going on. I noticed the following under /var/log/messages.log: +++ Jul 9 23:32:33 mini-0 pppd[1974]: Plugin rp-pppoe.so loaded. Jul 9 23:32:33 mini-0 pppd[1974]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5 Jul 9 23:32:34 mini-0 kernel: NET: Registered protocol family 10 Jul 9 23:32:34 mini-0 pppd[1974]: pppd 2.4.5 started by root, uid 0 Jul 9 23:32:34 mini-0 pppd[1974]: PPP session is 45128 Jul 9 23:32:34 mini-0 pppd[1974]: Connected to 00:12:7f:33:eb:3c via interface eth1 Jul 9 23:32:34 mini-0 pppd[1974]: Using interface ppp0 Jul 9 23:32:34 mini-0 pppd[1974]: Connect: ppp0 <--> eth1 Jul 9 23:32:34 mini-0 pppd[1974]: PAP authentication succeeded Jul 9 23:32:34 mini-0 pppd[1974]: peer from calling number 00:12:7F:33:EB:3C authorized Jul 9 23:32:34 mini-0 pppd[1974]: kernel does not support PPP filtering Jul 9 23:32:34 mini-0 pppd[1974]: local IP address 201.200.139.27 Jul 9 23:32:34 mini-0 pppd[1974]: remote IP address 200.91.104.9 Jul 9 23:32:34 mini-0 pppd[1974]: primary DNS address 200.91.75.6 Jul 9 23:32:34 mini-0 pppd[1974]: secondary DNS address 200.91.75.5 Jul 9 23:32:35 mini-0 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Jul 9 23:32:35 mini-0 kernel: nf_conntrack version 0.5.0 (7628 buckets, 30512 max) +++ It sounded curious that kernel does not support PPP filtering, but I'm almost certain that's not the issue, given that on the gateway (not the forwarded internal LAN), I can access all pages through firefox... Any help you can provide is very welcome... It might be the iptables is not working well. I missed to indicate this is running on a lemote mini-pc (archloong on mipsel), which of course has no official support, but I wanted to see first if I'm missing any configuration particular to arch (as I said this worked before also on a x86 arch box, but things change), so just in case perhaps someone identified the miss... Thanks, -- Javier.
[arch-general] grub-legacy-fedora-git package
Hi all, I have created a PKGBUILD for Fedora's GRUB Legacy fork, grub-legacy-fedora-git https://aur.archlinux.org/packages.php?ID=47959 . It includes support for GPT boot (not tested) and supports ext4 /boot (tested using the UEFI package). It does not include any of the patches used in core/grub package. It compiles fine with the binutils in Arch repos (unlike the current core/grub and aur/grub-gfx packages). It also supports splashimage (gfx) option. Although I maintain that package, I do not use it. I use grub2-bios-bzr which I maintain). Important info :- 1. The menu config file is /boot/grub/grub.conf, not /boot/grub/menu.lst . 2. The syntax for splashimage is (for example) - splashimage (hd0,0)/boot/grub/image.xpm.gz 3. The package builds fine in x86_64 with gcc-multilib. I have not checked whether it compiles without gcc-multilib (grub2 1.99 compiles without multilib in x86_64). Would be helpful if someone confirms whether it compiles in x86_64 without multilib. I request current core/grub and aur/grub-gfx users to test this package and give your comments/suggestions. Regards. Keshav PS: The equivalent UEFI package is grub-legacy-efi-fedora https://aur.archlinux.org/packages.php?ID=47979 .
Re: [arch-general] About a modprobe command before /etc/rc.sysinit
On 10.07.2011 12:18, F.Gr. wrote: > Hi, > during boot process, I'm getting the following (it seems there's a > problem with some modprobe command) before the script > '/etc/rc.sysinit' is run: > > --- > Usage: /sbin/modprobe [-v] [-V] [-C config-file] [-d ] [-n] > (cut) > --- > > I'm running the latest kernel version 2.6.39.3-1 on x86_64. > Will be fixed with mkinitcpio 0.7.2, but it doesn't cause any harm. -- Florian Pritz signature.asc Description: OpenPGP digital signature
Re: [arch-general] About a modprobe command before /etc/rc.sysinit
> > --- > Usage: /sbin/modprobe [-v] [-V] [-C config-file] [-d ] [-n] > (cut) > --- > I get that too. Im using systemd -- (\_ /) copy the bunny to your profile (0.o ) to help him achieve world domination. (> <) come join the dark side. /_|_\ (we have cookies.)
[arch-general] About a modprobe command before /etc/rc.sysinit
Hi, during boot process, I'm getting the following (it seems there's a problem with some modprobe command) before the script '/etc/rc.sysinit' is run: --- Usage: /sbin/modprobe [-v] [-V] [-C config-file] [-d ] [-n] (cut) --- I'm running the latest kernel version 2.6.39.3-1 on x86_64. -- The era of manufacturing consent has given way to the era of manufacturing news. Soon media newsrooms will drop the pretense, and start hiring theater directors instead of journalists. —Arundhati Roy
Re: [arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
10.7.2011 11.35 "Bogdan Ionuț" kirjoitti: > > On Sun, Jul 10, 2011 at 11:33, jesse jaara wrote: > > > nokms > > not nomodeset!? Oh sorry I did mean nomodeset. No wonder nokms looked like it was way too short. Also I assume you have loaded the fglrx module. Try to run just bare 'Xorg > ./x.log' so you get atleast somekind of an output saved for inspection.
Re: [arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
On Sun, Jul 10, 2011 at 11:33, jesse jaara wrote: > nokms not nomodeset!?
Re: [arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
Make sure you disable kms. Add 'nokms' kernel boot line
[arch-general] Xorg not working on AMD C-50 Fusion (Radeon HD 6250)
Hi all! I'm having trouble installing xorg on a Gateway Netbook which has a fusion AMD processor model "C-50". It has micro+graphics in one chip. I've googled that many people succeded with catalyst drivers, though I haven't been that lucky. I added the [catalyst] repo mentioned at the arch wiki, installed all xorg, xorg-utils, catalyst, catalyst-utils, etc. but I can't start x When running startx, nothing happens. It shows the prompt again. fglrxinfo returns "unable to open display (null)" /var/log/Xorg.0.log is empty , however, the same file with .old is at http://pastebin.archlinux.fr/433086 If helps, /etc/X11/xorg.conf is at http://pastebin.archlinux.fr/433085 Removing it makes no change. Well, any clue will be appreciated. Regards, Nicolás
