preupgrade or anaconda error
by Martín Marqués
I was trying to upgrade to F11-preview from F10. I was told to use
preupgrade instead of using yum, which passed the dependency problems
that stopped yum, but after rebooting anaconda gave errors which I was
unable to save. :-(
Couldn't connect to my wifi (which doesn't have encryption), nor was I
able to save it to disk (even though I saw the disks mounted).
I would like to give information on how anaconda crashed, but how? I
really want to test F11, and looks like preupgrade is a good tool to
accomplish it.
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador
15 years
Fix /boot/grub/grub.conf to chainload Fedora 11 Preview?? and Fedora 9 with chainloader
by Antonio Olivares
Dear fellow Fedoreans,
I have a machine which Windows, and Fedora 9 have coexisted happily since Fedora 9 was released. I shrunk the Windows Partition a bit more and setup an empty place where I installed Fedora 11 Preview(to update it to current Fedora 11 pre or rawhide whichever gets picked up via updates)
Now I can boot windows and Fedora 11, but can't boot Fedora 9, everything is in there I can see the data, I just can't boot it. Here's output of fdisk and grub.conf for both Fedora 9 and Fedora 11?? soon to be
root@slax:~# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005116a
Device Boot Start End Blocks Id System
/dev/sda1 1 9921 79688704 7 HPFS/NTFS
/dev/sda2 9922 14848 39576127+ 5 Extended
/dev/sda3 14849 14873 200812+ 83 Linux
/dev/sda4 14874 19457 36820980 8e Linux LVM
/dev/sda5 9922 10409 3919828+ 82 Linux swap
/dev/sda6 * 10410 10435 204799+ 83 Linux
/dev/sda7 10435 14848 35450879+ 8e Linux LVM
root@slax:~# cat /mnt/sda3/
System.map initrd-2.6.27.15-78.2.23.fc9.x86_64.img
System.map-2.6.26.1 initrd-2.6.27.19-78.2.30.fc9.x86_64.img
System.map-2.6.26.5 initrd-2.6.27.21-78.2.41.fc9.x86_64.img
System.map-2.6.27 initrd-2.6.27.7-53.fc9.x86_64.img
System.map-2.6.27.15-78.2.23.fc9.x86_64 initrd-2.6.27.img
System.map-2.6.27.19-78.2.30.fc9.x86_64 initrd-2.6.29.2.img
System.map-2.6.27.21-78.2.41.fc9.x86_64 lost+found/
System.map-2.6.27.7-53.fc9.x86_64 vmlinuz
System.map-2.6.29.2 vmlinuz-2.6.26.1
config-2.6.27.15-78.2.23.fc9.x86_64 vmlinuz-2.6.26.5
config-2.6.27.19-78.2.30.fc9.x86_64 vmlinuz-2.6.27
config-2.6.27.21-78.2.41.fc9.x86_64 vmlinuz-2.6.27.15-78.2.23.fc9.x86_64
config-2.6.27.7-53.fc9.x86_64 vmlinuz-2.6.27.19-78.2.30.fc9.x86_64
efi/ vmlinuz-2.6.27.21-78.2.41.fc9.x86_64
grub/ vmlinuz-2.6.27.7-53.fc9.x86_64
initrd-2.6.26.1.img vmlinuz-2.6.29.2
initrd-2.6.26.5.img
root@slax:~# cat /mnt/sda3/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,2)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.29.2)
root (hd0,2)
kernel /vmlinuz-2.6.29.2 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.29.2.img
title Fedora (2.6.27.21-78.2.41.fc9.x86_64)
root (hd0,2)
kernel /vmlinuz-2.6.27.21-78.2.41.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.27.21-78.2.41.fc9.x86_64.img
title Fedora (2.6.27.19-78.2.30.fc9.x86_64)
root (hd0,2)
kernel /vmlinuz-2.6.27.19-78.2.30.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.27.19-78.2.30.fc9.x86_64.img
title Fedora (2.6.27.15-78.2.23.fc9.x86_64)
root (hd0,2)
kernel /vmlinuz-2.6.27.15-78.2.23.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.27.15-78.2.23.fc9.x86_64.img
title Fedora (2.6.27.7-53.fc9.x86_64)
root (hd0,2)
kernel /vmlinuz-2.6.27.7-53.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.27.7-53.fc9.x86_64.img
title Fedora (2.6.27)
root (hd0,2)
kernel /vmlinuz-2.6.27 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.27.img
title Fedora (2.6.26.5)
root (hd0,2)
kernel /vmlinuz-2.6.26.5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.26.5.img
title Fedora (2.6.26.1)
root (hd0,2)
kernel /vmlinuz-2.6.26.1 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.26.1.img
title Microsoft Windows Vista Ultimate
rootnoverify (hd0,0)
chainloader +1
root@slax:~# cat /mnt/sda6/grub/gr
grub.conf grub.conf.bak
root@slax:~# cat /mnt/sda6/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,5)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_blackamd64home-lv_root
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,5)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.29.1-102.fc11.x86_64)
root (hd0,5)
kernel /vmlinuz-2.6.29.1-102.fc11.x86_64 ro root=/dev/mapper/vg_blackamd64home-lv_root rhgb quiet
initrd /initrd-2.6.29.1-102.fc11.x86_64.img
title windows
rootnoverify (hd0,0)
chainloader +1
title Fedora 9
rootnoverify (hd0,2)
chainloader +1
root@slax:~#
I have changed the rootnoverify (hd0,2) to rootnoverify (hd0,3) and have substituted 1, 2, 3, 4 and 5 and cannot boot. I get error 13 illegal ???
I have setup this before several times, at school I had a machine dual boot Fedora 9 and rawhide, but for some reason or another it is failing :(,
suggestions, advice, comments, are very much welcome.
Regards,
Antonio
15 years
Joining wireless and wired networks
by James Allsopp
Hi,
I've a computer at home I'm using for a network gateway, which has two
ethernet cards and a wireless card. One of the ethernet cards connects
to the outside world and the wireless side of the network connects to
the internet using iptables to provide NAT and forward the packets over.
The system is also running a dhcp server for the providing IP addresses
to the wireless clients.
What I want to do now is bring in the other ethernet card so computers
attached to that part of the network can connect to the internet and
access the services of the other machines on the network, regardless of
whether they're on the gateway or the wireless network.
I was considering bridging the wireless and the wired networks, but just
wanted to ask for opinions, other options. I''m loooking at eventually
getting a job working with linux systems, so it doesn't have to be a
"what would be best in a home environment" solution.
Thanks for the help,
James
15 years
postgresql f10 hangs on shutdown
by Michael Cronenworth
PostgreSQL hangs on shutdown causing me to have to hit the hardware
reset switch. Has anyone dealt with this issue? This has been occuring
to me for a long time, but since I cannot find much evidence as to why
it happens I haven't created a bug report.
Evidence so far:
-Before shutdown I can manually stop PostgreSQL successfully, but if I
forget and perform a shutdown/restart, it hangs on stopping postgresql.
-The process must be running for at least multiple hours. 4-8 hours
seems to be long enough. Otherwise it will shutdown OK.
-I don't even have to use a database for it to get into this bad state.
The shutdown process turns off NetworkManager, then sshd, then
postgresql, so I am unable to SSH in or log in to diagnose this issue.
Any pointers would be appreciated.
15 years
GPRS in Fedora 10
by Adeel Akbar
Hi I want to run internet through GPRS service. Can anyone advice how we create dial up connection in Fedora 10 to connect with internet.
Thanks & Regards
Adeel Akbar
15 years
I don't have colors in Midnight commander editor
by Mark Ryden
Hello,
I have fedora release 9 . I installed mc (midnight commander) by
"yum install mc".
When I open xml files or "c" source files or java with mc editor (by
pressing F4) I don't see any colors. (I mean colors of some keywords ,
like "int" (for c source file), lines starting with "<" or "<--" for
xml, etc.)
On other fedora machines I **do** see colors with mc.
Any ideas what can be the reason ?
Rgs,
Mark
15 years
flashgot and download helper
by Thufir
I'm using flashgot and download helper, plugins for firefox, to download
some vid's (flv's). I've browsed away from the videos and firefox is
just at no-javascript gmail, but the cpu is still pegged. top shows:
top - 20:41:18 up 1:37, 6 users, load average: 1.73, 2.12, 2.45
Tasks: 125 total, 1 running, 124 sleeping, 0 stopped, 0 zombie
Cpu(s): 15.9%us, 11.3%sy, 70.8%ni, 0.0%id, 1.0%wa, 0.7%hi, 0.3%si,
0.0%st
Mem: 480412k total, 444336k used, 36076k free, 6304k buffers
Swap: 2396712k total, 52464k used, 2344248k free, 180632k cached
PID to kill:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
COMMAND
15509 thufir 39 19 82052 10m 7772 S 15.6 2.2 0:00.47 totem-video-
thu
1930 root 20 0 77544 29m 7004 S 4.3 6.3 5:25.59
Xorg
2499 thufir 20 0 62608 16m 11m S 4.0 3.4 0:11.46 gnome-
terminal
2421 thufir 20 0 73024 17m 13m S 3.3 3.7 1:15.35
nautilus
2428 thufir 20 0 23136 9156 5200 S 3.0 1.9 0:41.24 imsettings-
appl
2547 thufir 20 0 242m 104m 22m S 1.3 22.3 14:07.14
firefox
However, I'm hesitant to kill totem. Is it involved in the download
somehow? The downloads are rather large and I'm not so keen to have the
CPU pegged for hours on end...
thanks,
Thufir
15 years
Re: WUSB54G firmware
by Jim
On 06/02/2009 07:36 PM, Terry Polzin wrote:
> On Sun, 2009-05-31 at 10:57 -0400, Jim wrote:
>
>> On 05/31/2009 09:05 AM, Terry Polzin wrote:
>>
>>> On Sat, 2009-05-30 at 21:47 -0400, Jim wrote:
>>>
>>>
>>>> FC10/Kde
>>>>
>>>> I'm trying to setup a Linksys WUSB54G and I get this error message from
>>>> DMESG.
>>>>
>>>> usb 2-2: firmware: requesting l3886usb
>>>>
>>>> usb 2-2: (p54usb) cannot find firmware (isl3886usb)
>>>>
>>>> usb 2-2: firmware: requesting isl3890usb
>>>>
>>>> p54usb: probe of 2-2:1.0 failed with error -2
>>>> usbcore: registered new interface driver p54usb
>>>>
>>>>
>>>> I have googled isl3886USB and can't find the firmware, does anyone know
>>>> where this firmware
>>>> is.
>>>>
>>>>
>>>>
>>> According to linuxwireless.org if your device is the same as listed
>>> below, you should be loading a prism 54 driver.
>>>
>>> p54usb Linksys WUSB54G 0x5041 0x2234
>>>
>>> run a lsusb and match up the hex values for vendor, product
>>>
>>>
>>>
>> It is loading and running the p54usb driver, but it also looking for the
>> 2.13.24.0.lm86(2).arm firmware.
>>
> Post o/p of ls -l /lib/firmware to the group.
>
>
>
15 years
Alternate to xawtv
by Bill Davidsen
Until xawtv gets working again, does someone have a suggestion for an alternate
software which runs on FC10-11 and can record video from webcam and supported
video cards?
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
15 years
