test March 2004

test@lists.fedoraproject.org

445 participants
732 discussions

x86_64 FC2T2 install (not)
by Jim Bevier 31 Mar '04

31 Mar '04

I tried to install from the new FC2T2 CDs but there are a few problems. 1. No release notes 2. No Upgrade option 3. Selecting manual or automatic Druid formatting cause the system to restart saying no install device is available. Next step? I have a ASUS K8V motherboard, AMD-64 3200+ processor, 1GB mem. FC1T1 is running on /dev/hdb7 partition.

2 1

RE: FC2 test2 is a BAD joke
by Ernest L. Williams Jr. 31 Mar '04

31 Mar '04

________________________________ From: fedora-test-list-bounces(a)redhat.com on behalf of Robert P. J. Day Sent: Tue 3/30/2004 6:59 AM To: For testers of Fedora Core development releases Subject: Re: FC2 test2 is a BAD joke On Tue, 30 Mar 2004, Douglas Furlong wrote: > On Tue, 2004-03-30 at 09:55, Manu Abraham wrote: > > It is not just the developer alone. Consider the people who download > > the ISO's over relatively slow links and try it on their machines, > > just to find their data just vanished. > I seem to sense a level of sarcasm in this particular sentence. > > These people that are downloading a test release over an extremely slow > link would have to have a fairly large desire to use a test release. for > what ever reason. I would have thought they would do this knowing that > it was a test release and as such may not work for every one. i have some sympathy with mr. abraham in this instance. there's nothing wrong with bugs in a beta/test release, and everyone realizes that. so we download it, install it, test it, find bugs, and keep updating as those bugs get shaken out. but all of that assumes you can get the software onto your machine in the first place. this suggests that, more than anything else, the installation procedure has to be flogged pretty hard before getting out the door to make sure it works. it's one thing to help test software once you get it onto your system. it's somewhat more serious to not even be able to get it onto your system to begin with, which goes a certain distance in explaining some folks' frustration level. ====================================================================== Sorry, I won't be so nice. I see this as plain negligence!! Who is in charge of Q/A?? And don't give the excuse that this is a test release, I am tired of hearing that excuse. ======================================================================= rday p.s. it's for precisely that reason that i asked previously, will there be a respin once this issue is resolved? under the circumstances, i don't see how there can't be. just my $0.02 canadian. (which, these days, is getting dangerously close to being $0.02 US. :-) -- fedora-test-list mailing list fedora-test-list(a)redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list

5 6

cardmgr: no sockets found!
by Konstantin Ryabitsev 31 Mar '04

31 Mar '04

Hello again, all: I just reinstalled my testing laptop with FC2T2 (it's been running the same, but continuously yum-upgraded from fc1). Now I can't get my pcmcia to work, when I try to start it, I get "Cardmgr: no sockets found!". Anyone seen this happen? This is a nothing-fancy p2-366 generic-brand laptop. Pcmcia has been working quite well on it since a long time ago. Regards, -- Konstantin ("Icon") Ryabitsev Duke Physics Systems Admin, RHCE I am looking for a job in Canada! http://linux.duke.edu/~icon/cajob.ptml

3 4

Booting from an ISO.
by Patrick 31 Mar '04

31 Mar '04

Is it possible to configure grub to boot from an ISO image on a harddrive partition? I'd like to try out FC2 Test2 but I'd rather not burn CDs which have such a short shelf-life. If I can find a way I'd like to create a 3GB partition and copy the FC2 Test2 DVD ISO there and then boot directly off of the ISO on that partition from grub. -- Patrick <pabos(a)glypsube.org>

3 2

FC2T2 Upgrade & SELinux
by Efthym 31 Mar '04

31 Mar '04

Hi List, I read in a previous posting that upgrading to T2 through yum will not enforce the SELinux policies. Does this apply to upgrading through the iso's as well ? Do I have to do a clean install to use SELinux ? Thanx

9 14

Re: Managing Fedora Testing
by Keith Lofstrom 31 Mar '04

31 Mar '04

Keith Lofstrom said: > ... > Instead, I would divide up the work into domains so that people can > choose a domain and test in that. Where to draw the line is difficult, > but I would probably make the domains "kernel and drivers", "installation > and update", "X and desktops", and "applications". Obviously, many > problems will cross domains, but to the extent that you can partition > things you reduce the scope of most problems. William Hooper replies: > What is preventing you from updating the "domain" you choose from Rawhide > and testing? Nothing prevents me from doing that, but it does not resemble my goal, which is to work with a group of like-minded individuals to locate functional and conceptual errors in a "distro" - that is, a collection of software packages that play well together. If all packages in a distro were autonomous and well behaved, then it would be easy to do as you say - in fact, there would not need to be a Fedora test team, just individual test teams associated with each package, checking conformance to specification. If there were just 20 packages in a distro, a domain system would not be useful, twenty items is easy to keep track of. But as it is, there are thousands of packages in the Fedora distro, with strong coupling between many. Without further partitioning, that is a recipe for engineering disaster. No mind is big enough to encompass all the interactions. So you break the problem down. "I am here to help" followed by "you're not good enough, go away" is OK if you want a late, hard-to-use, buggy distro. A response of "here, work on these things, leave me alone" is quite a bit more useful. I am proposing one way to partition useful testing tasks for the non-elite, a technique that works well in other fields. There are no doubt other techniques that work well, too. The testing performed so far by the elite has been incomplete, and focuses on install/kernel/code-structure issues rather than usage issues, because that is where this particular elite lives. Out here in the "other" world, where an error message should be a pointer to a config file rather than a source code file, somebody has to check whether the error messages really help Jane User fix her config files. The best person to do that is Jane. How can we help her participate? If she cannot participate, in what sense is this a community effort? If you limit debugging to a small subset of eyes, you will only find a small subset of bugs. The technical name for this approach is "Microsoft". Keith -- Keith Lofstrom keithl(a)ieee.org Voice (503)-520-1993 KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon" Design Contracting in Bipolar and CMOS - Analog, Digital, and Scan ICs

2 1

surprising success report
by Walker Aumann 31 Mar '04

31 Mar '04

My backup server has been a pain for years because it has an Adaptec AHA-2940U2W SCSI card along with an Adaptec AHA-2944UW SCSI card. Ever since the "new" aic7xxx module, that has meant booting in expert mode and manually selecting the appropriate driver (aic7xxx_old). On a lark, I tried booting this machine from the "notorious" FC2-test2 disc 1. Not only did it boot properly, but it figured out the SCSI cards well enough to get me to the disk partitioning menu (where I stopped because I'm not ready to install a test release on our backup server). With more results like this and being able to successfully configure SMTP authentication with postfix under FC2-test1 where I couldn't with RedHat 9, I'm really looking forward to this being ready for general use.

1 0

FC2T2 Initial Things
by Dan 31 Mar '04

31 Mar '04

Hi folks, I installed FC2t2 yesterday on my notebook (Compaq Presario 2133AC with AMD AthlonXP-M 2400+, 512MB, ATI Radeon Mobilty U1*, NatSemi Ethernet card and Orinoco_Pci WiFi) * Before you jump to conclusions, I know that this card is supposedly only supported in DRI-CVS etc as far as 3D is concerned, and I don't mind one bit (That will get fixed and working "enevtually"). I installed by downloading the boot.iso image and running "linux nousb nofirewire nopcmcia askmethod" from the boot: prompt. I need all those to get my keyboard to work in Anaconda (this is in bugzilla a number of times, and that is the solution...). Inistalled via my mirror (planetmirror.com) and went into things. For some reason (that eludes me now) I wanted to check what glxinfo said as far as my MESA/DRI setup went. *BANG* the X session went black and locked up cold (i didn't have an SSH connection into the box to find out what if anything was written on dmesg or the X log - I will post more updates today when I get the chance). The same thing happened when I tried to run a GL-based screensaver - it *should* have simply run with software rendering as all previous releases did, but instead just went to a blank screen and X locked up. This stuff is very reminiscent of when using testing/CVS IGP DRI, which I could never get working, despite all the claims that it did work. Is it possible that a) x11-org sees a radeon chipset and assumes that it can do 3d, even though it can't in practice, being an IGP? b) x11-org included some [broken] support for the IGP that nobody knows about? Anyway, I'll do more testing/work with FC2T2 today, and post more results. Cheers, Dan

1 0

SEL message
by Derek Tattersall 31 Mar '04

31 Mar '04

Using YUM update on FC2 test2 I get the following message: warning: setexeccon(root:staff_r:rpm_script_t) fails from context "root:staff_r:staff_t": Invalid argument It doesn't seem to cause a problem, (the security context is warning), but I am trying to come up to speed on SELinux and I've got a fair ways to go. Should I be worried about this message? What insufficiency on my part is causing it? Thanks, -- Derek Tattersall dlt(a)mebtel.net

2 1

A lot of problems with FC2 Test2 X64_64 - detailed description
by Alessandro Polverini 31 Mar '04

31 Mar '04

Hello, I installed it on a Asus K8V Delux with Athlon63 3200+ CPU, with 2 EIDE disks, 1 serial ATA disk, Sounblaster Audigy soundcard, GeForce FX5600XT. I had many blocking (and not) problems: *** During the install*** - Anaconda (and partitioner) does not detect /dev/hda! It only sees /dev/hdb and /dev/sda (sata disk) - I usually choose english language, but I use italian keyboard, I was not able to choose this one, but only the language - anaconda, after install asks "reboot", but it does not reboot. I had to use ctrl-alt-canc - Anaconda is unable to enter graphic mode, and all the install is done in text mode *** After the boot *** - In the file modprobe.conf there was a bad line: alias dmfe without the ethernet device. This is strange since upper in the file there was the correct line: alias eth2 dmfe - Kudzu starts and the kernel crashes completely telling (sorry. not cut&paste): Kernel bug at generic:664 Invalid operand: 0000[1] ... - After disabling automatic start of kudzu, I tried to configure graphic mode running system-config-display but it stops with this error: file "/usr/share/system-config-fisplay/xconf.py" line 412, in ? hardware_state.merge_into(xconfig) name error: name "hardware_state" is not defined - system-config-soundcard is unusable because it needs X - I loaded modules by hand, and then played a .ogg file with ogg123, I got this error: "Floating Point Exception" So, in practice, the system is unusable for me. Thanks, Alex P.S.: If you reply, please include my address since I'm not subscribed to the list.

5 6

← Newer
1
...
5
6
7
8
9
10
11
...
74
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

test March 2004