Re: RPM DB corruption with F-16 Beta

2011-10-14 Thread Bojan Smojver
Panu Matilainen laiskiainen.org> writes: > "It gave a bunch of > errors and recovery blew it up" is not sufficient information to attempt > analyzing what went wrong. Yeah, I'm aware of that. I just wanted to find out whether someone else experienced something similar, before I cry foul. This

Re: RPM DB corruption with F-16 Beta

2011-10-14 Thread Bojan Smojver
drago01 gmail.com> writes: > Radeons < r300 are not supported so you will end up with fallback mode. Ah, OK. That explains it then. Thanks. -- Bojan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Re: RPM DB corruption with F-16 Beta

2011-10-14 Thread Bojan Smojver
Panu Matilainen laiskiainen.org> writes: > Makes me wonder why is rpmdb open attempted at reboot... Not sure, to be honest. > What type of install was this btw - plain old manual installation with > anaconda, kickstart or install from Live CD? Plain old install from a DVD. -- Bojan -- dev

Re: RPM DB corruption with F-16 Beta

2011-10-14 Thread drago01
On Fri, Oct 14, 2011 at 4:32 AM, Kevin Kofler wrote: > Bojan Smojver wrote: >> Even more interestingly, dmesg and Xorg.0.log contain all the right >> things and yet, mutter won't start. I guess being in Intel graphics camp >> for some time now made me unfamiliar with radeon driver. > > It might be

Re: RPM DB corruption with F-16 Beta

2011-10-14 Thread Panu Matilainen
On 10/13/2011 03:36 AM, Bojan Smojver wrote: > On Thu, 2011-10-13 at 11:15 +1100, Bojan Smojver wrote: >> Let's see whether this is something that can be replicated. > > When the installation finished and I pressed the reboot button, a > message flashed briefly at the bottom of the screen. Somethin

Re: RPM DB corruption with F-16 Beta

2011-10-14 Thread Peter Robinson
On Fri, Oct 14, 2011 at 9:39 AM, Panu Matilainen wrote: > On 10/13/2011 01:30 AM, Bojan Smojver wrote: >> This is probably not worthy of a bug report, but may still be useful to >> confirm a problem that someone else may have experienced. >> >> I resurrected an old notebook (HP Pavilion ZE4201) to

Re: RPM DB corruption with F-16 Beta

2011-10-14 Thread Panu Matilainen
On 10/13/2011 01:30 AM, Bojan Smojver wrote: > This is probably not worthy of a bug report, but may still be useful to > confirm a problem that someone else may have experienced. > > I resurrected an old notebook (HP Pavilion ZE4201) to test some stuff > under relatively low memory conditions (768

Re: RPM DB corruption with F-16 Beta

2011-10-13 Thread Kevin Kofler
Bojan Smojver wrote: > Even more interestingly, dmesg and Xorg.0.log contain all the right > things and yet, mutter won't start. I guess being in Intel graphics camp > for some time now made me unfamiliar with radeon driver. It might be blacklisted in mutter/gnome-shell because of known driver is

Re: RPM DB corruption with F-16 Beta

2011-10-12 Thread Bojan Smojver
On Thu, 2011-10-13 at 11:44 +1100, Bojan Smojver wrote: > Interestingly, the IGP 340M (RS200) ATI graphics hardware is still not > supported for 3D stuff. Just FYI. Even more interestingly, dmesg and Xorg.0.log contain all the right things and yet, mutter won't start. I guess being in Intel graphi

Re: RPM DB corruption with F-16 Beta

2011-10-12 Thread Bojan Smojver
On Thu, 2011-10-13 at 09:30 +1100, Bojan Smojver wrote: > HP Pavilion ZE4201 Interestingly, the IGP 340M (RS200) ATI graphics hardware is still not supported for 3D stuff. Just FYI. -- Bojan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/de

Re: RPM DB corruption with F-16 Beta

2011-10-12 Thread Bojan Smojver
On Thu, 2011-10-13 at 11:15 +1100, Bojan Smojver wrote: > Let's see whether this is something that can be replicated. When the installation finished and I pressed the reboot button, a message flashed briefly at the bottom of the screen. Something like: RPM database cannot be opened. So, it looked

Re: RPM DB corruption with F-16 Beta

2011-10-12 Thread Bojan Smojver
On Thu, 2011-10-13 at 09:30 +1100, Bojan Smojver wrote: > Installed F-16 Beta i686 onto it with no trouble whatsoever. Installing again, this time I picked the updates repository as well. Let's see whether this is something that can be replicated. -- Bojan -- devel mailing list devel@lists.fe

Re: RPM DB corruption with F-16 Beta

2011-10-12 Thread Bojan Smojver
John Reiser bitwagon.com> writes: > > I resurrected an old notebook (HP Pavilion ZE4201) to test some stuff > > under relatively low memory conditions (768 MB on the box). > > This can be simulated on any larger machine by appending " mem=768m" > (note all lower case) to the end of the kernel bo

Re: RPM DB corruption with F-16 Beta

2011-10-12 Thread John Reiser
> I resurrected an old notebook (HP Pavilion ZE4201) to test some stuff > under relatively low memory conditions (768 MB on the box). This can be simulated on any larger machine by appending " mem=768m" (note all lower case) to the end of the kernel boot command line. -- -- devel mailing list d

RPM DB corruption with F-16 Beta

2011-10-12 Thread Bojan Smojver
This is probably not worthy of a bug report, but may still be useful to confirm a problem that someone else may have experienced. I resurrected an old notebook (HP Pavilion ZE4201) to test some stuff under relatively low memory conditions (768 MB on the box). Installed F-16 Beta i686 onto it with