Re: laptop install - screen gets white
by Rainer Hattenhauer
>Hm, that bug is marked as CLOSED RAWHIDE. Are you sure that 'nofb'
>is still not mentioned in help? If not them maybe #89722 should
>be reopened.
Sorry, again. Seems that my eyes were covered by tomatos, like we're saying
here in germany. Of cause, it is mentioned in help.
But wouldn't it be better to boot for installation issues in safe state by
default (e.g. using nofb), I think most of the system will work with this
option out of the box (?)
Greetings
Raienr
20 years, 8 months
automated build tool for an src.rpm tree ?
by Balint Cristian
Hi !
Have someone developed a tool or have knowledge of some perl/python scripted stuff for
automated build of a src.rpm tree wich inteligently compute dependency and start compiling/installing
packages step by step in right order till whole tree is compiled and installed.
PS: dont need to knoledge even some bug hunting skill :)))
Thanks a lot,
Cristian
--
Life in itself has no meaning.
Life is an opportunity to create meaning.
\|/ ____ \|/
"@'/ .. \`@"
/_| \__/ |_\
\__U_/
20 years, 8 months
Boot Problem
by Ozkan ALTUNER
Hi,
I downloaded and installed severn. After successful installation it doesn't
boot at all. I see the graphical boot screen but when it comes to "starting
printing system" it hangs.
How can i solve it?
Thanks,
Ozkan
20 years, 8 months
Re: Graphical boot issues: a.o. graphical boot twice slower then text
by Rainer Hattenhauer
>Since the X display has more resolution, the graphical boot has the
>potential to provide more information. However, what is usually done is to
>use the graphical boot to _hide_ information, for warmth and fuzziness.
>This should be an option if people want it, but it would also be nice if
>the graphical boot could be configured to display lots of info including
>every ugly error that occurs. I would use the graphical boot if this was
>possible. Also, unless there's some issue I'm not aware of, the shutdown
>should be the same type as the bootup, for symmetry. Right now, it appears
>that shutdown only has text mode.
The SuSE guys have included the possibility to press F2 during boot up /
shutdown of the system, so every old fashioned guy (like me) who wants to
see the boot / shutdown messages is able to see them in a window included in
the graphical area. I don't know if they are holding a software patent for
this issue, like others do for scroll bars ;-)
Perhaps one could include this to the fedora bootup, too.
Rainer
20 years, 8 months
RE: Grub stage1 file error
by Ossama Khayaat
Sorry, but I just hate the 'install from scratch', because I used to do
it a lot in Windoze and try to run away from it :)
In a way, you're right. It works just fine. I tried installing it on
another machine and had no problem at all. Seems like I'll just wait for
the next beta/final release, and try again on the laptop. You know, I
don't want to format/install too much on it.
Thanks,
Ossama
> -----Original Message-----
> From: Robert L Cochran [mailto:cochranb@speakeasy.net]
> Sent: Sunday, October 05, 2003 3:20 PM
> To: fedora-test-list(a)redhat.com
> Subject: Re: Grub stage1 file error
>
> Yes I know, it seems odd to be told to do it again from scratch. But
> this is a beta release. You don't seem to have found a solution to the
> issue you are having yet. Sometimes doing it all over again tells you
if
> it is really a reproducible problem. I haven't yet had a problem with
> grub during this beta, but I haven't been very active either. Most of
my
> attention is going into experimenting with wireless networking. You
have
> probably done more with the beta than I.
>
> Bob
>
>
> Ossama Khayaat wrote:
> >>-----Original Message-----
> >>From: Robert L Cochran [mailto:cochranb@speakeasy.net]
> >>Subject: Re: Grub stage1 file error
> >>
> >>I don't know why Grub didn't install correctly on your machine. The
> >>installer is usually good about doing that. My suggestion is to
> >>reinstall Fedora Core from scratch. You should be able to accept the
> >>default anaconda options. Just click 'next' to go to the next
screen.
> >
> >
> > But this isn't a solution, i.e. to just reinstall from scratch! And
I
> > already accepted the default settings for grub.
> >
> >
> >>All the Grub problems I've experienced are related to booting
multiple
> >>operating systems. In the case of just a single OS (Fedora Core) you
> >>should be fine without changing any options at first.
> >
> >
> > I've been using GRUB since version 7.3, and never had a problem with
it,
> > specially that I use multiple OSs (sometimes even more than one
Linux
> > distro). Furthermore, I used to configure it manually for multiple
linux
> > system, so I have no issue with it at all.
> >
> >
> >>Later on, once you are booting successfully, and only if you need
> >
> > this,
> >
> >>edit /boot/grub.conf to pass acpi=on to the kernel so your
networking
> >>will work.
> >
> >
> > Never had to do this as well, since the start.
> > The problem here refers to the stage1 file.
> >
> > Thanks for your answer.
> > Ossama
> >
> >
> > --
> > fedora-test-list mailing list
> > fedora-test-list(a)redhat.com
> > http://www.redhat.com/mailman/listinfo/fedora-test-list
> >
> >
>
> --
> Bob Cochran
> Greenbelt, Maryland, USA
> http://greenbeltcomputer.biz/
>
>
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-test-list
20 years, 8 months
RE: Grub stage1 file error
by Ossama Khayaat
> -----Original Message-----
> From: Robert L Cochran [mailto:cochranb@speakeasy.net]
> Subject: Re: Grub stage1 file error
>
> I don't know why Grub didn't install correctly on your machine. The
> installer is usually good about doing that. My suggestion is to
> reinstall Fedora Core from scratch. You should be able to accept the
> default anaconda options. Just click 'next' to go to the next screen.
But this isn't a solution, i.e. to just reinstall from scratch! And I
already accepted the default settings for grub.
> All the Grub problems I've experienced are related to booting multiple
> operating systems. In the case of just a single OS (Fedora Core) you
> should be fine without changing any options at first.
I've been using GRUB since version 7.3, and never had a problem with it,
specially that I use multiple OSs (sometimes even more than one Linux
distro). Furthermore, I used to configure it manually for multiple linux
system, so I have no issue with it at all.
> Later on, once you are booting successfully, and only if you need
this,
> edit /boot/grub.conf to pass acpi=on to the kernel so your networking
> will work.
Never had to do this as well, since the start.
The problem here refers to the stage1 file.
Thanks for your answer.
Ossama
20 years, 8 months
nvidia and severn2 -- an alternative
by Robert P. J. Day
rather than messing with CC=gcc32 or IGNORE_CC_MISMATCH, here's an
alternative way of installing your nvidia drivers (at least, it works for
me, so i'm open to corrections/clarifications).
download the latest nvidia driver from www.nvidia.com,
NVIDIA-Linux-x86-1.0-4496-pkg2.run. don't try to install it, just extract
it into a directory with:
$ sh NV...run --extract-only
now, as root, "cd" into that directory and just run "make install". that
should build the driver and install it. because you're actually compiling
the driver, you're pretty likely to not have to worry about any compiler
mismatches.
but wait -- there's more.
if you're running the 2.6.0-xxx kernel, go to www.minion.de, and grab
the single diff file NVIDIA_kernel-1.0-4496-2.6.diff. (note: while i'm
grateful for that site, i find the explanation there virtually
incomprehensible.)
apply that single diff file against the nvidia directory you extracted,
in the subdirectory .../usr/src/nv, then create the single symlink
Makefile -> Makefile.kbuild. return to the top level nvidia directory
and, once again,
# make install
every time you boot under a new kernel, the previous nvidia module won't
be any good, so just head back to your nvidia directory and rerun "make
isntall".
i use this constantly as i like to keep up with the 2.6.0 bk patches.
thoughts? it's actually a pretty straightforward process once you get
it down, it supports the 2.6,0 kernel, and i never have to mess with
compiler version issues.
rday
20 years, 8 months
Fedora Core Test 2 full screen issues
by James Drabb
Can anyone run mpalyer/gmplayer in full screen under 0.94 in Gnome? It
used to work fine in RH 9. I tried to watch a DVD and an mpeg at full
screen, however the panel at the top of the screen stays on top. If I
remove that panel and put it anywhere else, it works fine. Are there
any settings to make this panel NOT topmost?
Jim Drabb
--
James Drabb
Senior Programmer Analyst
Davenport, FL USA
JDrabb_REMOVE(a)tampabay.rr.com
20 years, 8 months
(no subject)
by VENKAT RAMANAN
after doing all the updates through up2date my login welcome screen is
crashing . it reverts to the default faisafe gnome welcome screen. i am not
able to start kde session as it again reverts to faisafe gnome welcome
screen. Any idea how to restore it?
ramanan
_________________________________________________________________
Three simple steps. They guarantee your safety.
http://server1.msn.co.in/features/general/SMBvirus/index.asp Protect
yourself against the SMB.EXE virus.
20 years, 8 months