Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
i got lost in your mail... but i do see from your subject that you should use `pacman -Syu` and not just `pacman -Su`, as the package database wont be updated without `y`... and for blank screen, maybe try kernel option `nomodeset`... and in next mail try to be more precise what you did and what happens... as you talk about pop-ups, did you install xorg ? are you using a DE ? which gfx driver you installed for xorg ?...
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
On Sun, Jul 04, 2010 at 11:51:12AM +0200, Andre Osku Schmidt wrote: i got lost in your mail... but i do see from your subject that you should use `pacman -Syu` and not just `pacman -Su`, as the package database wont be updated without `y`... and for blank screen, maybe try kernel option `nomodeset`... and in next mail try to be more precise what you did and what happens... as you talk about pop-ups, did you install xorg ? are you using a DE ? which gfx driver you installed for xorg ?... The popups are those generated by the monitor when it doesn't get a valid signal. Having a Sony as well they sound familiar to me. Things seem to go wrong well before Xorg gets involved. The nomodeset option willl probably provide a working system in RL 3. Once that is working we can have a closer look. Ciao, -- Je veux que la mort me trouve plantant mes choux, mais nonchalant d’elle, et encore plus de mon jardin imparfait. (Michel de Montaigne)
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
It would appear that on Jul 4, Andre Osku Schmidt did say: i got lost in your mail... but i do see from your subject that you should use `pacman -Syu` and not just `pacman -Su`, as the package database wont be updated without `y`... Sorry for my natural wordyness but I do have a hard time with brevity. If I hadn't been trying to keep that book down to a couple of chapters I'd have mentioned that I use pacman Sy as a separate command. It's nice that I could combine them into a single command. But on some systems I still use apt-get, and my ingrained habit of starting with a separate refresh command keeps me out of trouble. and for blank screen, maybe try kernel option `nomodeset`... and in next mail try to be more precise what you did and what happens... OK I'll try that on my next reboot cycle. (just have to finish a few E-mail chores first.) I'll let you know what happens... as you talk about pop-ups, did you install xorg ? are you using a DE ? which gfx driver you installed for xorg ?... f...@kokkinizita.net nailed that one... I did think that my overlong text did specify that the pop-ups came from the monitor, but Like you said, you got lost in my post. (Sorry) It would appear that on Jul 4, f...@kokkinizita.net did say: On Sun, Jul 04, 2010 at 11:51:12AM +0200, Andre Osku Schmidt wrote: as you talk about pop-ups, did you install xorg ? are you using a DE ? which gfx driver you installed for xorg ?... The popups are those generated by the monitor when it doesn't get a valid signal. Having a Sony as well they sound familiar to me. Things seem to go wrong well before Xorg gets involved. The nomodeset option willl probably provide a working system in RL 3. Once that is working we can have a closer look. ABSOLUTELY. my next task _was_ supposed to be to open a lynx session on one console open to the wiki to remind myself HOW to use another console to get x working on an arch install... (This is only my second arch install ever. The first, on my laptop has worked out fairly well for me.) But I did have X running on that before they stopped passing control of the video back and forth between the kernel and the xserver. (Did I understand correctly that such control now resides only in the kernel whether x is up or not?) But in any case even when I do get X working I won't allow ANY display manager to control my boot/login process. If they take away startx I'll likely give up X before I'll use GDM, KDM, Entrance (etc...) Any graphical login prompt always makes me so uncomfortable that I forget why I was booting the durned computer in the first place. Heck I even insist on a text based grub menu for similar reasons. When I'm ready to put up with a GUI, I use startx, and not until... Still Like I told Osku, I'll try that nomodeset kernel option and post the results in this thread. Thanks for the help guys. -- | --- ___ | 0 - Joe (theWordy) Philbrook | ^ J(tWdy)P |~\___/~ jtw...@ttlc.net
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
On Sun, Jul 04, 2010 at 08:15:26AM -0400, Joe(theWordy)Philbrook wrote: But in any case even when I do get X working I won't allow ANY display manager to control my boot/login process. If they take away startx I'll likely give up X before I'll use GDM, KDM, Entrance (etc...) Any graphical login prompt always makes me so uncomfortable that I forget why I was booting the durned computer in the first place. Heck I even insist on a text based grub menu for similar reasons. When I'm ready to put up with a GUI, I use startx, and not until... I'm using XDM which is relatively painless compared to GDM, KDM and friends. With a modified 'Arch' setup it can be made to look nice. Hint: once you have RL3, make sure you have the network and sshd configured and running before doing anything X11. That way you can always log in from another machine if startx leaves the system in an unusable state. It can save a lot of rebooting time... I wonder if you aleady have nouveau installed. Do an lsmod | grep nouveau to check. Nouveau is the new open source driver for Nvidia cards. Unlike nv it is a kernel module, not an Xorg driver and that can be confusing if you're not aware of it. If it is installed, it will be used even before you start X, and the only way to prevent that (if you want X to use another driver) seems to blacklist the module in /etc/rc.conf. The failing modeset could be because you have nouveau and it's doing the wrong thing, or because you don't have it... For X you will have the choice of nv, nouveau, or the proprietary nvidia driver. Nouveau is reported to work well, but on some systems I had to revert to nv to get usable audio latency. This seems to depend on the video card type as on other audio system here nouveau works just fine. Ciao, -- Je veux que la mort me trouve plantant mes choux, mais nonchalant d’elle, et encore plus de mon jardin imparfait. (Michel de Montaigne)
[arch-general] hid2hci tool missing
Hello altogether I am trying to get the bluetooth adapter of my dell latitude latpop to work. In many tutorials I have read of the tool hid2hci. Unfortunatelly this doesn't seem to be on my system and I can't find it elsewhere. I have bluez and bluez-utils installed. Any ideas which package might contain hid2hci? Thanks Benedikt
Re: [arch-general] hid2hci tool missing
On 4 July 2010 07:22, b1 fo...@b1online.de wrote: Hello altogether I am trying to get the bluetooth adapter of my dell latitude latpop to work. In many tutorials I have read of the tool hid2hci. Unfortunatelly this doesn't seem to be on my system and I can't find it elsewhere. I have bluez and bluez-utils installed. Any ideas which package might contain hid2hci? # pacman -S pkgtools ... $ pkgfile hid2hci core/udev $ pacman -Ql udev | grep hid2hci /lib/udev/hid2hci So it's in the udev package, which you probably already have installed, just under a weird path. Thanks Benedikt -- Tavian Barnes
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
It would appear that on Jul 4, f...@kokkinizita.net did say:
I'm using XDM which is relatively painless compared to
GDM, KDM and friends. With a modified 'Arch' setup it
can be made to look nice.
What looks nice to me is the console login prompt...
Also aside from that, there's another reason I use startx (with a wrapper
script that copies the appropiate file to ~/.xinitrc depending on which
desktop...) Which is usually E17 which can remember where to put a konsole
window based {in part} on the name which I can feed to it with a
running terminal application via a line like this in the ~/.xinitrc...
konsole --workdir ~/mail --name F2alpine --profile BlackGray -e alpine
I've yet to find a DE that will remember enough details of a konsole window
in it's saved sessions method to prestart the correct application(s) in the
correct konsole windows etc...
I don't suppose XDM can be configured to use a ~/.xinitrc like script that
will let me prestart selected terminal applications in a simular manor?
Hint: once you have RL3, make sure you have the network
and sshd configured and running before doing anything X11.
That way you can always log in from another machine if
startx leaves the system in an unusable state. It can
save a lot of rebooting time...
Well I've evidentaly got the internet as fetchmail is working... Though it
said my comcast cablemodem connection to comcast's pop server was insecure.
It said something about verisign not being trusted?
sshd is another matter. My personal paranoia settings require NEVER
allowing ANY remote logins. If God himself want's to use my computer he
dang well better be using the attached keyboard, or there's gonna be
trouble... grin
I wonder if you aleady have nouveau installed. Do an
lsmod | grep nouveau
to check.
Since I haven't yet remembered how to get gdm working in arch, I redirected
that output to a file in lieu of pasteing it into the message. Since I
compose with vim that means :r nouveau.out
nouveau 477159 0
ttm38517 1 nouveau
drm_kms_helper 21512 1 nouveau
drm 131562 3 nouveau,ttm,drm_kms_helper
i2c_algo_bit4319 1 nouveau
i2c_core 15144 5
nouveau,drm_kms_helper,i2c_nforce2,drm,i2c_algo_bit
button 3738 1 nouveau
Nouveau is the new open source driver for Nvidia cards.
Unlike nv it is a kernel module, not an Xorg driver and
that can be confusing if you're not aware of it. If it
is installed, it will be used even before you start X,
and the only way to prevent that (if you want X to use
another driver) seems to blacklist the module in
/etc/rc.conf.
The failing modeset could be because you have nouveau
and it's doing the wrong thing, or because you don't
have it...
I say I'm not sure but I think the above output says I do have it and that
it must be doing the wrong thing...
For X you will have the choice of nv, nouveau, or the
proprietary nvidia driver. Nouveau is reported to work
well, but on some systems I had to revert to nv to get
usable audio latency. This seems to depend on the video
card type as on other audio system here nouveau works
just fine.
Since this is my first Nvidia card AND I'm NOT a gamer, I woiuldn't know
what to do with any of the above. But since (I think) Arch now favors,
ummnnn, What's it called? a, Oh good I found some of my notes: KMS
it would make sense to try to configure the kernal module driver first
wouldn't it? Is there a how-to that doesn't expect me to be a computer
science grad?
By the way, I noticed a couple of odd things durring this nomodeset session.
Don't know if they are symptoms of problems or possibly the results of
having used the nomodxeset kernel option...
1) durring the boot, it said it couldn't load the sun12x22.psfu.gz font
I'd prespecified in my rc.conf... Actualy on the assumption that KMS was
going to notice my high reasolution monitor I figgured I'd likely need
something like ter-128n.psf.gz Like I wound up using in my laptop. But I
haven't installed the terminus font package yet... So the biggest I
expected to start with was one of the 12x22 fonts...
I note that even without loading the large font, I wound up with a large
text size on my hi-res monitor (yup an actual 80 column display) So maybe
the nomodeset option is why the 12x22 font didn't load?
2) a little more disturbing I note that when I switched to another tty and
logged in to another console session, it hungup without executing the
.bash_profile... If I hit ^C I got a default command prompt but my .bashrc
set command path wasn't working untill I used the bash command to open a
subshell... Could the nomodeset option be responsible for this???
3) WHA-DA-{censored} Now I notice I can't get mc to fire up. I used it
earlier in this login session, But now the tty just hangs, and I need to
use another tty to issue a killall mc to get my prompt back... I'm not
[arch-general] ftp.gigabit.nu / ftp.archlinux.se shutting down
Cut from the forum where my co-admin first put this up, however it got closed with reason trolling... This mirror will shut down in the upcoming days. Few funny facts: * We never got contacted by anyone before we got added in the official mirror list. We just posted this thread and all of the sudden it appeared. No verification of whom we were and what our intension were. * ArchLinux is fundamentally unscalable in the package manager aspect. * ArchLinux puts the trust in the hands of every mirror owner and their security. ftp.archlinux.se is the prime example of a machine vulnerable to all sorts of things. This affect YOUR security. This is why it's being put down. If the ArchLinux authors would start signing packages this would not be a risk to you. * We posted a suggestion of this in 2006. http://bugs.archlinux.org/task/5331 -- This is 4 years of insecurity. * We recommend all of you to switch to a distribution caring about user security and atleast signs their packages. Most RPM and APT based distros does this (Ubuntu, Debian, RedHat, CentOS, SuSE, OpenSuSE, etc etc etc). Have fun. :-) Yours, Mikael Rickard
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
On 05/07/10 07:08, Joe(theWordy)Philbrook wrote: It would appear that on Jul 4, f...@kokkinizita.net did say: I'm using XDM which is relatively painless compared to GDM, KDM and friends. With a modified 'Arch' setup it can be made to look nice. I've yet to find a DE that will remember enough details of a konsole window in it's saved sessions method to prestart the correct application(s) in the correct konsole windows etc... I don't suppose XDM can be configured to use a ~/.xinitrc like script that will let me prestart selected terminal applications in a simular manor? You could try slim, is graphical login manager which uses .xinitrc It works well for me, looks good and very lightweight. Ross.
Re: [arch-general] ftp.gigabit.nu / ftp.archlinux.se shutting down
On 04/07/10 21:35, Rickard Eriksson wrote: Cut from the forum where my co-admin first put this up, however it got closed with reason trolling... This mirror will shut down in the upcoming days. Few funny facts: * We never got contacted by anyone before we got added in the official mirror list. We just posted this thread and all of the sudden it appeared. No verification of whom we were and what our intension were. * ArchLinux is fundamentally unscalable in the package manager aspect. * ArchLinux puts the trust in the hands of every mirror owner and their security. ftp.archlinux.se is the prime example of a machine vulnerable to all sorts of things. This affect YOUR security. This is why it's being put down. If the ArchLinux authors would start signing packages this would not be a risk to you. * We posted a suggestion of this in 2006. http://bugs.archlinux.org/task/5331 -- This is 4 years of insecurity. * We recommend all of you to switch to a distribution caring about user security and atleast signs their packages. Most RPM and APT based distros does this (Ubuntu, Debian, RedHat, CentOS, SuSE, OpenSuSE, etc etc etc). Have fun. :-) Yours, Mikael Rickard It's true, you are trolling.
Re: [arch-general] ftp.gigabit.nu / ftp.archlinux.se shutting down
On 07/04/2010 10:48 PM, Nathan Wayde wrote: On 04/07/10 21:35, Rickard Eriksson wrote: Cut from the forum where my co-admin first put this up, however it got closed with reason trolling... This mirror will shut down in the upcoming days. Few funny facts: * We never got contacted by anyone before we got added in the official mirror list. We just posted this thread and all of the sudden it appeared. No verification of whom we were and what our intension were. * ArchLinux is fundamentally unscalable in the package manager aspect. * ArchLinux puts the trust in the hands of every mirror owner and their security. ftp.archlinux.se is the prime example of a machine vulnerable to all sorts of things. This affect YOUR security. This is why it's being put down. If the ArchLinux authors would start signing packages this would not be a risk to you. * We posted a suggestion of this in 2006. http://bugs.archlinux.org/task/5331 -- This is 4 years of insecurity. * We recommend all of you to switch to a distribution caring about user security and atleast signs their packages. Most RPM and APT based distros does this (Ubuntu, Debian, RedHat, CentOS, SuSE, OpenSuSE, etc etc etc). Have fun. :-) Yours, Mikael Rickard It's true, you are trolling. I'm afraid not, the hostnames has already been removed and the server is being shutdown. However, I guess you could call the suggestions trolling of some kind however.. Best regards Rickard Eriksson
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
On Sun, Jul 04, 2010 at 03:08:05PM -0400, Joe(theWordy)Philbrook wrote:
What looks nice to me is the console login prompt...
Also aside from that, there's another reason I use startx (with a wrapper
script that copies the appropiate file to ~/.xinitrc depending on which
desktop...) Which is usually E17 which can remember where to put a konsole
window based {in part} on the name which I can feed to it with a
running terminal application via a line like this in the ~/.xinitrc...
konsole --workdir ~/mail --name F2alpine --profile BlackGray -e alpine
I've yet to find a DE that will remember enough details of a konsole window
in it's saved sessions method to prestart the correct application(s) in the
correct konsole windows etc...
You'r mixing up several things here: 1) starting X, 2) starting a
window manager or desktop environment, and 3) restoring or setting
up that desktop for a particular user.
If you use a 'graphical' login like XDM then (1) is already done when
you login. If you use startx after logging in it's your job to keep
those things apart (or not).
I don't suppose XDM can be configured to use a ~/.xinitrc like script that
will let me prestart selected terminal applications in a simular manor?
As used here XDM will call ~/.xession, you can put whatever you
want in there. I use it to map some keys, then start WindowMaker.
sshd is another matter. My personal paranoia settings require NEVER
allowing ANY remote logins. If God himself want's to use my computer he
dang well better be using the attached keyboard, or there's gonna be
trouble... grin
There may be situations where such paranoia is warranted, but in
general this just means you're making your own life more difficult
than it should be. A ssh login can be set up to require a 1024 or
more bit cryptographic token - if that isn't enough nothing will
ever be.
I say I'm not sure but I think the above output says I do have it and that
it must be doing the wrong thing...
Looks like it...
1) durring the boot, it said it couldn't load the sun12x22.psfu.gz font
I'd prespecified in my rc.conf... Actualy on the assumption that KMS was
going to notice my high reasolution monitor I figgured I'd likely need
something like ter-128n.psf.gz Like I wound up using in my laptop. But I
haven't installed the terminus font package yet... So the biggest I
expected to start with was one of the 12x22 fonts...
I note that even without loading the large font, I wound up with a large
text size on my hi-res monitor (yup an actual 80 column display) So maybe
the nomodeset option is why the 12x22 font didn't load?
The 80 column display is what 'nomodeset' is supposed to do. You
could try the old 'vga' option to switch to a higher resolution
even with nomodeset - AFAIK it will work.
2) a little more disturbing I note that when I switched to another tty and
logged in to another console session, it hungup without executing the
.bash_profile... If I hit ^C I got a default command prompt but my .bashrc
set command path wasn't working untill I used the bash command to open a
subshell... Could the nomodeset option be responsible for this???
Don't thing so, but I noticed ~/.bash_profile being ignored as well.
~/.profile will probably work.
3) WHA-DA-{censored} Now I notice I can't get mc to fire up. I used it
earlier in this login session, But now the tty just hangs, and I need to
use another tty to issue a killall mc to get my prompt back... I'm not sure
what changed since I started this Arch session. But something don't seam
stable...
I don't have any idea as to what 'mc' is...
Ciao,
--
Je veux que la mort me trouve plantant mes choux, mais
nonchalant d’elle, et encore plus de mon jardin imparfait.
(Michel de Montaigne)
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
On Mon, 2010-07-05 at 08:44 +1200, Ross wrote: On 05/07/10 07:08, Joe(theWordy)Philbrook wrote: It would appear that on Jul 4, f...@kokkinizita.net did say: I'm using XDM which is relatively painless compared to GDM, KDM and friends. With a modified 'Arch' setup it can be made to look nice. I've yet to find a DE that will remember enough details of a konsole window in it's saved sessions method to prestart the correct application(s) in the correct konsole windows etc... I don't suppose XDM can be configured to use a ~/.xinitrc like script that will let me prestart selected terminal applications in a simular manor? You could try slim, is graphical login manager which uses .xinitrc It works well for me, looks good and very lightweight. Ross. Its also not really maintained I think, hence the existance of slim-plus in the AUR.
Re: [arch-general] ftp.gigabit.nu / ftp.archlinux.se shutting down
* We recommend all of you to switch to a distribution caring about user security and atleast signs their packages. Most RPM and APT based distros does this (Ubuntu, Debian, RedHat, CentOS, SuSE, OpenSuSE, etc etc etc). -- LOL does he think any of us are actually going to switch to one of the above distros..? Although nothing wrong with them, used them all for desktops and still for servers..
Re: [arch-general] ftp.gigabit.nu / ftp.archlinux.se shutting down
On 07/04/2010 11:35 PM, Rickard Eriksson wrote: Cut from the forum where my co-admin first put this up, however it got closed with reason trolling... This mirror will shut down in the upcoming days. Few funny facts: snip i must say that is a very professional attempt to inform developers and admins that actually organize our mirroring schema and access to rsync. in the future, for other projects i suggest to use bugtracker, contact the leader of the project or use a mailing list that it supposed to handle this kind of announcement. p.s imo this is lack of respect and i don't believe that you actually handle a mirror dropping like that for other projects. -- Ionuț
Re: [arch-general] [arch-dev-public] [PATCH 1/2] checkpkg: Use temporary working directory
On 05/07/10 04:18, Eric Bélanger wrote:
Signed-off-by: Eric Bélangersnowmanisc...@gmail.com
---
checkpkg |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/checkpkg b/checkpkg
index 47fb672..7765d80 100755
--- a/checkpkg
+++ b/checkpkg
@@ -27,6 +27,12 @@ if [ $arch == 'any' ]; then
CARCH='any'
fi
+TEMPDIR=$(mktemp /tmp/checkpkg-script.)
+rm $TEMPDIR
+mkdir -p $TEMPDIR
mktemp can be called with the -d switch and it will create a directory
instead of a file. I believe that's the preferable way to go about it.
+
+cd $TEMPDIR
+
for _pkgname in ${pkgna...@]}; do
pkgfile=${_pkgname}-${pkgver}-${pkgrel}-${CARCH}${PKGEXT}
oldstylepkgfile=${_pkgname}-${pkgver}-${pkgrel}${PKGEXT}
@@ -90,3 +96,5 @@ for _pkgname in ${pkgna...@]}; do
echo No filename differences for $_pkgname.
fi
done
+
+echo Files saved to $TEMPDIR
Re: [arch-general] [arch-dev-public] [PATCH 1/2] checkpkg: Use temporary working directory
On Sun, Jul 4, 2010 at 9:25 PM, Evangelos Foutras foutre...@gmail.com wrote: On 05/07/10 04:18, Eric Bélanger wrote: Signed-off-by: Eric Bélangersnowmanisc...@gmail.com --- checkpkg | 8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/checkpkg b/checkpkg index 47fb672..7765d80 100755 --- a/checkpkg +++ b/checkpkg @@ -27,6 +27,12 @@ if [ $arch == 'any' ]; then CARCH='any' fi +TEMPDIR=$(mktemp /tmp/checkpkg-script.) +rm $TEMPDIR +mkdir -p $TEMPDIR mktemp can be called with the -d switch and it will create a directory instead of a file. I believe that's the preferable way to go about it. Agree. I had just copied that snippet from the lddd script. If this patch is accepted, I'll sumbit another patch to use the -d option in both scripts.
[arch-general] [signoff] hdparm-9.29-1
Hi guys, bump to latest version, added wiper.sh script. please signoff both arches greetings tpowa -- Tobias Powalowski Archlinux Developer Package Maintainer (tpowa) http://www.archlinux.org tp...@archlinux.org signature.asc Description: This is a digitally signed message part.
