Ambarish Sridharanarayanan wrote:
> Fixed the problem by
>
> * downloading debug symbols for tigervnc
> * extracting symbol files (rpm2cpio)
> * attaching gdb to the running Xvnc process and with the help of the symbol
> file, changing idleTimeOut to 1 sec, so that the stale connection would be
On Sun, 29 Aug 2010, Ambarish Sridharanarayanan wrote:
> I'm trying to install Fedora 13 over VNC [1], with TigerVNC on Windows as
> the VNC client. In the middle, my connection dropped; when reconnecting,
> TigerVNC tells me "The server is already in use". Looking at the sources,
> it looks like
I'm trying to install Fedora 13 over VNC [1], with TigerVNC on Windows as the
VNC client. In the middle, my connection dropped; when reconnecting, TigerVNC
tells me "The server is already in use". Looking at the sources, it looks like
the XVnc thinks there's an active connection, and it looks li
> From: Harald Hoyer
> You might want to edit /etc/grub.conf in rescue and remove "quiet" and
> "rhgb" and add "rdinit rd_NO_PLYMOUTH" to the Kernel command line.
I will gladly do it but it seam to be a non editable file, if there is
away please let me know.
My apology I was try to use a wrong
> From: Harald Hoyer
> You might want to edit /etc/grub.conf in rescue and remove "quiet" and
> "rhgb" and add "rdinit rd_NO_PLYMOUTH" to the Kernel command line.
I will gladly do it but it seam to be a non editable file, if there is
away please let me know.
>
> On Wednesday, July 21, 2010, Vi
You might want to edit /etc/grub.conf in rescue and remove "quiet" and
"rhgb" and add "rdinit rd_NO_PLYMOUTH" to the Kernel command line.
On Wednesday, July 21, 2010, Vincent Onelli wrote:
>> From: "Darr"
>
>> >> H... if grub's boot menu never appears, how do you know
>> >> there's only 1 ke
> From: "Darr"
> >> H... if grub's boot menu never appears, how do you know
> >> there's only 1 kernel listed in it?
> >>
> >> If grub's boot menu never appears, how do you choose to run
> >> windows or fedora?
> >>
> > By looking in the directory /lib/modules, while I am in the command
>
>
On Tuesday, 20 July, 2010 @17:22 zulu, Vincent Onelli scribed:
>> H... if grub's boot menu never appears, how do you know
>> there's only 1 kernel listed in it?
>>
>> If grub's boot menu never appears, how do you choose to run
>> windows or fedora?
>>
> By looking in the directory /lib/modules
> From: "Darr"
> On Tuesday, 20 July, 2010 @01:00 zulu, Vincent Onelli scribed:
>
> > I couldn't not remove any thing. Grub.conf apparently is a non
> > editable file
>
> we were not advising to edit the grub.conf file.
>
> If the kernel arguments from the boot menu are edited, they
> return
On Tuesday, 20 July, 2010 @01:00 zulu, Vincent Onelli scribed:
> I couldn't not remove any thing. Grub.conf apparently is a non
> editable file
we were not advising to edit the grub.conf file.
If the kernel arguments from the boot menu are edited, they
return to 'normal' at next boot.
Another w
> From: "Darr"
> Subject: Re: Fedora 13 installation, does not boot
> On Sunday, 18 July, 2010 @14:24 zulu, Vincent Onelli scribed:
>
> > By runing depmod -a I got the following:
> > WARNING: Couldn't open directory /lib/modules/2.6.33.3-85.fc13.i686:
&
> From: Harald Hoyer
> Subject: Re: Fedora 13 installation, does not boot
> On 07/18/2010 04:24 PM, Vincent Onelli wrote:
> >> From: "Darr"
> >> On Saturday, 17 July, 2010 @23:56 zulu, Vincent Onelli scribed:
> >>
> >>> I used the re
On 07/18/2010 04:24 PM, Vincent Onelli wrote:
>> From: "Darr"
>> On Saturday, 17 July, 2010 @23:56 zulu, Vincent Onelli scribed:
>>
>>> I used the rescue disk typed: chroot /mnt/sysimage
>>> then dracut -f /boot/initramfs-$(uname -r).img $(uname -r) and got the
>>> fallowing answer:
>>> find:'/lib/
On Sunday, 18 July, 2010 @14:24 zulu, Vincent Onelli scribed:
> By runing depmod -a I got the following:
> WARNING: Couldn't open directory /lib/modules/2.6.33.3-85.fc13.i686:
> no such file or directory.
> FATAL: could not
> open /lib/modules/2.6.33.3-85.fc13.i686/modules.dep.temp for writing:
>
> From: "Darr"
> On Saturday, 17 July, 2010 @23:56 zulu, Vincent Onelli scribed:
>
> > I used the rescue disk typed: chroot /mnt/sysimage
> > then dracut -f /boot/initramfs-$(uname -r).img $(uname -r) and got the
> > fallowing answer:
> > find:'/lib/modules/2.6.33.3-85.fc13.i686/':no such file or
On Saturday, 17 July, 2010 @23:56 zulu, Vincent Onelli scribed:
> I used the rescue disk typed: chroot /mnt/sysimage
> then dracut -f /boot/initramfs-$(uname -r).img $(uname -r) and got the
> fallowing answer:
> find:'/lib/modules/2.6.33.3-85.fc13.i686/':no such file or directory
Follow that same
On 07/17/2010 10:17 AM, Chris Rouch wrote:
> On 17 July 2010 15:57, Vincent Onelli wrote:
>> Hello,
>>
>> I installed f13 on Dell dimension 8300 (with two HD 120GB for windows
>> end 320GB for Fedora) several time with 32 bit iso file downloaded from
>> 3 different place bit torrent, the iso fil
> 14. Re: Fedora 13 installation, does not boot (Chris Rouch)
> From: Chris Rouch
> On 17 July 2010 15:57, Vincent Onelli wrote:
> >
> > Hello,
> >
> > I installed f13 on Dell dimension 8300 (with two HD 120GB for windows
> > end 320GB for Fedora) sever
On Saturday, July 17, 2010, Chris Rouch wrote:
>
> It could be that your initramfs file is corrupt - it doesn't have
> references to the correct disks.
By default, nothing is hardcoded by dracut in the initramfs.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscr
On 17 July 2010 15:57, Vincent Onelli wrote:
>
> Hello,
>
> I installed f13 on Dell dimension 8300 (with two HD 120GB for windows
> end 320GB for Fedora) several time with 32 bit iso file downloaded from
> 3 different place bit torrent, the iso file to install on dvd, and
> another side 32 bit 3.1
Hello,
I installed f13 on Dell dimension 8300 (with two HD 120GB for windows
end 320GB for Fedora) several time with 32 bit iso file downloaded from
3 different place bit torrent, the iso file to install on dvd, and
another side 32 bit 3.1GB.
The first one from bit torrent on reboot display erro
Hello,
I installed f13 on Dell dimension 8300 (with two HD 120GB for windows
end 320GB for Fedora) several time with 32 bit iso file downloaded from
3 different place bit torrent, the iso file to install on dvd, and
another side 32 bit 3.1GB.
The first one from bit torrent on reboot display error
On 13/07/10 01:35 AM, Tom H wrote:
>
> grub2 can boot from an lvm'd /boot; it needs an "insmod lvm".
Aha! Wonderful news. I have just started using LVM and this is quite
helpful. When I was reading up on LVM, many sources had trouble with
/boot on an LVMed partition so I created /boot in a non-LV
On Mon, Jul 12, 2010 at 2:39 PM, H.S. wrote:
> On 12/07/10 01:42 PM, Rick Stevens wrote:
>>
>> /dev/sdc5 is an extended partition. IIRC, update-grub only checks
>> primary partitions--primarily because your BIOS can't boot anything in
>> an extended partition, either.
>
> hmm .. then why does it
On Mon, Jul 12, 2010 at 1:42 PM, Rick Stevens wrote:
> On 07/12/2010 10:20 AM, H.S. wrote:
>> On 12/07/10 12:50 PM, Suvayu Ali wrote:
>>> On Monday 12 July 2010 08:08 AM, H.S. wrote:
I am using LVM. F13 is installed with its / mounted on
/dev/mapper/vg1-lv8 and its boot on /dev/sdc5. Upd
On Mon, Jul 12, 2010 at 1:49 PM, Suvayu Ali wrote:
> On Monday 12 July 2010 10:20 AM, H.S. wrote:
>> On 12/07/10 12:50 PM, Suvayu Ali wrote:
>>> On Monday 12 July 2010 08:08 AM, H.S. wrote:
I am using LVM. F13 is installed with its / mounted on
/dev/mapper/vg1-lv8 and its boot on /dev/sd
On 07/12/2010 11:39 AM, H.S. wrote:
> On 12/07/10 01:42 PM, Rick Stevens wrote:
>>
>>
>> /dev/sdc5 is an extended partition. IIRC, update-grub only checks
>> primary partitions--primarily because your BIOS can't boot anything in
>> an extended partition, either.
>
> hmm .. then why does it detect
On 12/07/10 11:08 AM, H.S. wrote:
> On a newly installed Debian Testing system, I installed Fedora 13 in a
> different partition but chose not to install the boot loaded since I
> wanted to use Debian's boot loader for all OSes.
>
> Now when I do update-grub in Debian, it detects all OSes installe
On 07/12/2010 11:39 AM, Tom Horsley wrote:
> On Mon, 12 Jul 2010 10:42:01 -0700
> Rick Stevens wrote:
>
>> /dev/sdc5 is an extended partition.
>
> I boot from extended partitions all the time. I've never
> noticed that the bios cared.
Directly from the BIOS or via an intermediary such as grub or l
On Mon, 12 Jul 2010 10:42:01 -0700
Rick Stevens wrote:
> /dev/sdc5 is an extended partition.
I boot from extended partitions all the time. I've never
noticed that the bios cared.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedo
On 12/07/10 01:42 PM, Rick Stevens wrote:
>
>
> /dev/sdc5 is an extended partition. IIRC, update-grub only checks
> primary partitions--primarily because your BIOS can't boot anything in
> an extended partition, either.
hmm .. then why does it detect OSes on my LVM volumes? I don't think
BIOS c
On Monday 12 July 2010 11:10 AM, H.S. wrote:
> On 12/07/10 01:49 PM, Suvayu Ali wrote:
>>
>> I am not well versed with grub, but have you checked whether you have
>> the correct "device.map" file?
>>
>
> How do I check that? device.map file is something that I have never had
> to deal with before (
On 07/12/2010 10:20 AM, H.S. wrote:
> On 12/07/10 12:50 PM, Suvayu Ali wrote:
>> On Monday 12 July 2010 08:08 AM, H.S. wrote:
>>> I am using LVM. F13 is installed with its / mounted on
>>> /dev/mapper/vg1-lv8 and its boot on /dev/sdc5. Update-grub appears to
>>> miss detecting the kernels in /dev/s
On 12/07/10 01:49 PM, Suvayu Ali wrote:
>
> I am not well versed with grub, but have you checked whether you have
> the correct "device.map" file?
>
How do I check that? device.map file is something that I have never had
to deal with before (Red Hat (7, 8, 9), Fedora Core and Fedora till ver.
9
On Monday 12 July 2010 10:20 AM, H.S. wrote:
> On 12/07/10 12:50 PM, Suvayu Ali wrote:
>> On Monday 12 July 2010 08:08 AM, H.S. wrote:
>>> I am using LVM. F13 is installed with its / mounted on
>>> /dev/mapper/vg1-lv8 and its boot on /dev/sdc5. Update-grub appears to
>>> miss detecting the kernels
On 12/07/10 12:50 PM, Suvayu Ali wrote:
> On Monday 12 July 2010 08:08 AM, H.S. wrote:
>> I am using LVM. F13 is installed with its / mounted on
>> /dev/mapper/vg1-lv8 and its boot on /dev/sdc5. Update-grub appears to
>> miss detecting the kernels in /dev/sdc5 altogether. Any idea why is
>> that? I
On Monday 12 July 2010 08:08 AM, H.S. wrote:
> I am using LVM. F13 is installed with its / mounted on
> /dev/mapper/vg1-lv8 and its boot on /dev/sdc5. Update-grub appears to
> miss detecting the kernels in /dev/sdc5 altogether. Any idea why is
> that? Is there is a bug in Fedora 13?
>
I think its
On a newly installed Debian Testing system, I installed Fedora 13 in a
different partition but chose not to install the boot loaded since I
wanted to use Debian's boot loader for all OSes.
Now when I do update-grub in Debian, it detects all OSes installed in
the hard drives connected to the system
Jerry,
Thanks a lot!
but this is not the case.
The things is that it keeps rebooting over and over again
after hanging for a while! I should have mentioned it, sorry.
Rgs,
Mark
On Sat, Jun 5, 2010 at 11:30 PM, Jerry Feldman wrote:
> On 06/05/2010 02:43 AM, Mark Ryden wrote:
>> Hello,
>> I had
On 06/05/2010 02:43 AM, Mark Ryden wrote:
> Hello,
> I had tried to install Fedora 13 on Lenovo N500 latpop and when I try to
> boot
> it starts, the fedora logo appears, some services (like udev) are
> started, and then
> it hangs; I tried it three times. I added to the kernel boot
> parameters
Hello,
I had tried to install Fedora 13 on Lenovo N500 latpop and when I try to boot
it starts, the fedora logo appears, some services (like udev) are
started, and then
it hangs; I tried it three times. I added to the kernel boot
parameters "noprobe noapic noapci" but
it did not help.
This laptop
On Wed, May 26, 2010 at 3:42 PM, Leslie S Satenstein
wrote:
>
> I had to let you know how I passed a night of no sleep to install Fedora13.
>
> My Configuration.
> disk hd0, XP on 1st half, Fedora12 on second.
> Disk hd1 W7 on 1st half, storage (fat32) on second half
>
> CPU memory 4 gigs, ATI
I had to let you know how I passed a night of no sleep to install Fedora13.
My Configuration.
disk hd0, XP on 1st half, Fedora12 on second.
Disk hd1 W7 on 1st half, storage (fat32) on second half
CPU memory 4 gigs, ATI video card, and Intel e7300 dual core cpu. DVD Burner,
etc.
I decided
43 matches
Mail list logo
