devel December 2005

devel@lists.stg.fedoraproject.org

222 participants
213 discussions

mock how-to?
by Gilboa Davara 26 Dec '05

26 Dec '05

Hello all, Can anybody point me to a good mock (Fedora's build environment) HOW-TO? The main mock site (http://fedoraproject.org/wiki/Projects/Mock) is a bit lacking... Gilboa

3 3

testing PCMCIA setup under FC5, for Sierra Aircard555 CMDA modem (url's updated)
by Kevin Verma 26 Dec '05

26 Dec '05

Hello, I am very excited about the newer PCMCIA implementation in accord with hotplug. I was trying to setup my Sierra Wireless Aircard 555 under FC5 test1 and hit the obvious bumps. Below is a URL where I have documented some of my understanding for the newer systems as it works: http://www.bloglines.com/blog/kevinverma?id=39 Below a URL where Rahul S. has added to the Fedora Release notes overview: http://fedoraproject.org/wiki/Docs/Beats/OverView After patching (as on blog_url above) the serial_cs.c, I noticed that this PCMCIA device reports different manufacture_id on FC4 and FC5, further I noticed the same is happening on FC5 box before and after manual firmware loading as below in command line snippet. Before you look into the snippet below I will also like to point out that confused about different manufacture_id reporting I re-patched the serial_cs.c and below is what is being used for the snippet bellow, here: +PCMCIA_DEVICE_CIS_MANF_CARD(0x013f, 0xa555, "SW_555_SER.cis"), /* Sierra Aircard 555 CDMA 1xrtt Modem */ ---snip from FC5 test1 start--- [root@server1 ~]# pccardctl eject [root@server1 ~]# pccardctl insert [root@server1 ~]# pccardctl info PRODID_1="Sierra Wireless" PRODID_2="AirCard 555" PRODID_3="A555" PRODID_4="Rev 1" MANFID=0192,a555 FUNCID=6 [root@server1 ~]# wvdialconf foo.conf Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Port Scan<*1>: S1 S2 S3 S4 S5 S6 S7 S8 Port Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16 Port Scan<*1>: S17 S18 S19 S20 S21 S22 S23 S24 Port Scan<*1>: S25 S26 S27 S28 S29 S30 S31 Sorry, no modem was detected! Is it in use by another program? Did you configure it properly with setserial? Please read the FAQ at http://open.nit.ca/wvdial/ If you still have problems, send mail to wvdial-list(a)lists.nit.ca. [root@server1 ~]# pcmcia-socket-startup [root@server1 ~]# wvdialconf foo.conf Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Port Scan<*1>: S1 S2 S3 S4 S5 S6 S7 S8 Port Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16 Port Scan<*1>: S17 S18 S19 S20 S21 S22 S23 S24 Port Scan<*1>: S25 S26 S27 S28 S29 S30 S31 Sorry, no modem was detected! Is it in use by another program? Did you configure it properly with setserial? Please read the FAQ at http://open.nit.ca/wvdial/ If you still have problems, send mail to wvdial-list(a)lists.nit.ca. [root@server1 ~]# cat /lib/firmware/SW_555_SER.cis > /sys/class/pcmcia_socket/pcmcia_socket0/cis [root@server1 ~]# pcmcia-socket-startup [root@server1 ~]# wvdialconf foo.conf Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS1<*1>: ATQ0 V1 E1 -- OK ttyS1<*1>: ATQ0 V1 E1 Z -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyS1<*1>: Modem Identifier: ATI -- ERROR ttyS1<*1>: Max speed is 115200; that should be safe. ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK Port Scan<*1>: S3 S4 S5 S6 S7 S8 S9 S10 Port Scan<*1>: S11 S12 S13 S14 S15 S16 S17 S18 Port Scan<*1>: S19 S20 S21 S22 S23 S24 S25 S26 Port Scan<*1>: S27 S28 S29 S30 S31 Found a modem on /dev/ttyS1. Modem configuration written to foo.conf. ttyS1<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" [root@server1 ~]# less wvdial.conf [root@server1 ~]# vim wvdial.conf [root@server1 ~]# pccardctl info PRODID_1="Sierra Wireless" PRODID_2="AirCard 555" PRODID_3="A555" PRODID_4="Rev 1" MANFID=013f,0710 FUNCID=2 [root@server1 ~]# ---snip FC5 test1 end--- the virsions if you want to know are: 2.6.14-prep (kernel-2.6.14-1.1783_FC5 - src) pcmciautils-011-1 hotplug-2004_09_23-10 So finally this modem seems ready on expected ttyS1 and ready for connection to be established, I'll also liek to have any suggestions how this can be more fine tuned automatic further, and some help for understating the manufacture_id issue. Thanks,

1 0

testing PCMCIA setup under FC5, for Sierra Aircard555 CMDA modem
by Kevin Verma 26 Dec '05

26 Dec '05

Hello, I am very excited about the newer PCMCIA implementation in accord with hotplug. I was trying to setup my Sierra Wireless Aircard 555 under FC5 test1 and hit the obvious bumps. Below is a URL where I have documented some of my understanding for the newer systems as it works: my_blog_url_ Below a URL where Rahul S. has added to the Fedora Release notes overview: rahul_fc_wiki_url_ After patching (as on blog_url above) the serial_cs.c, I noticed that this PCMCIA device reports different manufacture_id on FC4 and FC5, further I noticed the same is happening on FC5 box before and after manual firmware loading as below in command line snippet. Before you look into the snippet below I will also like to point out that confused about different manufacture_id reporting I re-patched the serial_cs.c and below is what is being used for the snippet bellow, here: +PCMCIA_DEVICE_CIS_MANF_CARD(0x013f, 0xa555, "SW_555_SER.cis"), /* Sierra Aircard 555 CDMA 1xrtt Modem */ ---snip from FC5 test1 start--- [root@server1 ~]# pccardctl eject [root@server1 ~]# pccardctl insert [root@server1 ~]# pccardctl info PRODID_1="Sierra Wireless" PRODID_2="AirCard 555" PRODID_3="A555" PRODID_4="Rev 1" MANFID=0192,a555 FUNCID=6 [root@server1 ~]# wvdialconf foo.conf Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Port Scan<*1>: S1 S2 S3 S4 S5 S6 S7 S8 Port Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16 Port Scan<*1>: S17 S18 S19 S20 S21 S22 S23 S24 Port Scan<*1>: S25 S26 S27 S28 S29 S30 S31 Sorry, no modem was detected! Is it in use by another program? Did you configure it properly with setserial? Please read the FAQ at http://open.nit.ca/wvdial/ If you still have problems, send mail to wvdial-list(a)lists.nit.ca. [root@server1 ~]# pcmcia-socket-startup [root@server1 ~]# wvdialconf foo.conf Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Port Scan<*1>: S1 S2 S3 S4 S5 S6 S7 S8 Port Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16 Port Scan<*1>: S17 S18 S19 S20 S21 S22 S23 S24 Port Scan<*1>: S25 S26 S27 S28 S29 S30 S31 Sorry, no modem was detected! Is it in use by another program? Did you configure it properly with setserial? Please read the FAQ at http://open.nit.ca/wvdial/ If you still have problems, send mail to wvdial-list(a)lists.nit.ca. [root@server1 ~]# cat /lib/firmware/SW_555_SER.cis > /sys/class/pcmcia_socket/pcmcia_socket0/cis [root@server1 ~]# pcmcia-socket-startup [root@server1 ~]# wvdialconf foo.conf Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS1<*1>: ATQ0 V1 E1 -- OK ttyS1<*1>: ATQ0 V1 E1 Z -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyS1<*1>: Modem Identifier: ATI -- ERROR ttyS1<*1>: Max speed is 115200; that should be safe. ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK Port Scan<*1>: S3 S4 S5 S6 S7 S8 S9 S10 Port Scan<*1>: S11 S12 S13 S14 S15 S16 S17 S18 Port Scan<*1>: S19 S20 S21 S22 S23 S24 S25 S26 Port Scan<*1>: S27 S28 S29 S30 S31 Found a modem on /dev/ttyS1. Modem configuration written to foo.conf. ttyS1<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" [root@server1 ~]# less wvdial.conf [root@server1 ~]# vim wvdial.conf [root@server1 ~]# pccardctl info PRODID_1="Sierra Wireless" PRODID_2="AirCard 555" PRODID_3="A555" PRODID_4="Rev 1" MANFID=013f,0710 FUNCID=2 [root@server1 ~]# ---snip FC5 test1 end--- the virsions if you want to know are: 2.6.14-prep (kernel-2.6.14-1.1783_FC5 - src) pcmciautils-011-1 hotplug-2004_09_23-10 So finally this modem seems ready on expected ttyS1 and ready for connection to be established, I'll also liek to have any suggestions how this can be more fine tuned automatic further, and some help for understating the manufacture_id issue. Thanks,

1 0

VMWare tools on Fedora Core 5
by William Lovaton 25 Dec '05

25 Dec '05

Hello, I've been doing some testing of RawHide on a virutal machine I configured a few days ago with VMWare 5.5.1 build-19175. Every thing is working fine except that I can't install the VMWare tools on the guess operating system to improve performance and imrpove the display settings so I can use a decent resolution, right now am stuck with 800 x 600. Any idea about how to install the VMWare tools on FC5 guess OS? when I try to do it gnome-volume-manager crashes and it doesn't do anything, any attempt to restart g-v-m results in a immediate crash. The only way to fix it is to cancel the installation of the VMWare tools and then g-v-m can be started normally again. I hope it can be done because that performance gain would be great, all in all I am very impressed with FC5 performance. Cheers, -William ___________________________________________________________ Do You Yahoo!? La mejor conexión a Internet y <b >2GB</b> extra a tu correo por $100 al mes. http://net.yahoo.com.mx

8 17

Merry Christmas!
by Marcus Hartig 25 Dec '05

25 Dec '05

Merry Christmas to all Fedora developers and users! Enjoy the time with the family! Best wishes and regards, Marcus

1 0

ssh to a FC5 test1 system fails, fails to create pts device nodes with 2.6.14-1.1783
by Kevin Verma 25 Dec '05

25 Dec '05

Hello, I updated the kernel to kernel-2.6.14-1.1783_FC5 on a FC5 test1 machine, and after reboot I could not log on to it via ssh, the error message in log files were as following: (hand typed) tailf -f /var/log/secure sshd (pid): Accepted public key for root from 192.168.0.3 sshd (pid): pam_unix(sshd:session): session opened for user root by (uid=0) sshd (pid): error: openpty: no such file or directory sshd (pid): session_pty_req: session 0 alloc failed Looking into /dev/pts/ , there are zero files. I'll like to know if this report has got attention of the kernel package developers and to suggest an intermediate fix. Cheers,

3 4

Too much time wasted installing fedora on raid1
by Paul P Komkoff Jr 24 Dec '05

24 Dec '05

Hello. Last N systems I've installed, I am usually assembling software raid1 at install time. The disk layout I'm using is trivial: 100MB + the rest, where on 1st 100MB is /dev/md0 (ext3, /boot) and the rest is /dev/md1 (lvm, other). For whatever reason (haven't looked at the code yet :() anaconda issuing mdadm commands in such order that primary replica of unsynched md0 is second drive, and raid1 resync started first on md1. So, to boot without changing bios settings back and forth (or without disabling 1st disk drive by any other means) it is nesessary to wait while md1 raid1 resyncs, which can be as long as 2 hours (250GB HDD). I've not tried fc5 test1 yet, but I'm pretty sure that without any additional steps to reslove this issue it couldn't just vaporize. So, is it possible to change anaconda wrt described issue? -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head

12 24

Random X crashes: fact or fiction?
by Bojan Smojver 23 Dec '05

23 Dec '05

As of about 2-3 weeks ago, I'm seeing random crashes of X under heavy load (e.g. kernel compile in an xterm, Firefox, Evolution being started etc. - all under Gnome). X simply dies and I end up on VT1, after which X gets restarted (i.e. GDM). Obviously, all the processes running inside X die too. This is with up-to-date Rawhide in i686 with Radeon IGP M340. The most recent crash was during kernel compile this morning, with all the recent packages. Before I start digging around trying to figure out how to report this for real, just wanted to check if there are other people that have observed similar stuff with recent X. Just making sure I'm not going crazy here... -- Bojan

1 0

Re: Royalty free gstreamer plug-in
by Sean 23 Dec '05

23 Dec '05

On Fri, December 23, 2005 11:41 am, Sean said: > Hmmm I don't pretend to understand this stuff, but the GPL text seems > pretty clear on this matter: > > "For example, if a patent license would not permit royalty-free > redistribution of the Program by all those who receive copies directly or > indirectly through you, then the only way you could satisfy both it and > this License would be to refrain entirely from distribution of the > Program." > > So the only question is, is the gstreamer mp3 plugin patent free or not? > Doh, this doesn't really apply since nobody is trying to distribute this code under the GPL... nevermind.. i'll leave this debate to brighter legal minds than me.. Sean

1 0

KDE 3.5
by Eric Tanguy 23 Dec '05

23 Dec '05

I would like to know why this version was pushed directly in FC-4 and not in update-testing before. This would avoid the problem with k3b!! Now we have to wait a k3b update to make it run. Thanks Eric

6 6

← Newer
1
2
3
4
5
6
7
8
9
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel December 2005