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
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
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?
Just enable the alsa daemon in rc.conf so that sound levels get reloaded on
boot according to what they were at shutdown time. ^^
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 fo
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.archlin
>> 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 o
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
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.
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. Th
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
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 wa
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
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
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.
>
> Fo
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 lat
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
iptable
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 c
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
>
> ---
> 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.)
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 er
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'
On Sun, Jul 10, 2011 at 11:33, jesse jaara wrote:
> nokms
not nomodeset!?
Make sure you disable kms. Add 'nokms' kernel boot line
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 wik
25 matches
Mail list logo
