Fedora13 showed 128 TB /proc/kcore on 2GB RAM
by Chen, Helen Y
Hi,
I am running Fedora 13 with the 2.6.33.5-112-2.2 kernel, and am trying to make an ISO image of my hard disk for other use. Unfortunately "mkisofs" failed because /proc/kcore exceeded its 4GB file size limit. In fact, the size of the kcore on my system is shown to be 128TB, and the machine itself only contains 2GB of RAM. Has anyone experienced the same problem? BTW, the kcore files on my redhat machines reflect the actual RAM size as it should be. Also, does anyone know why "mkisofs" even tries to copy a virtual file into the ISO image it is creating?
Thanks,
H Chen
13 years, 11 months
Intel 82852/855GM and fc13 problems with videos
by Gianluca Cecchi
Hello,
trying to configure F13 x86 on an old laptop for a friend of mine, tired of
WIndows viruses and problems; the pc is a Dell Latitude D505
ALso basically works apart from video and video contnts in browser...
lspci says
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated
Graphics Device (rev 02)
default config (no xorg.conf) works well in general, but unable to handle
videos (with both mplayer and totem); also in flash.
for example starting mplayer I get its window witg blue backgroubd and X
Windows System freezes
I can switch to a terminal and see this in messages:
Jul 14 22:06:18 popi kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck
timer elapsed... GPU hung
Jul 14 22:06:18 popi kernel: render error detected, EIR: 0x00000000
Jul 14 22:06:18 popi kernel: [drm:i915_do_wait_request] *ERROR*
i915_do_wait_request returns -5 (awai
ting 142311 at 142310)
Trying init 3 - init 5 I get black screen with an arrow in the middle (that
I can move around with mouse... ) and I have to restart to be able to use
graphical env again.
In messages I have also, when system starts:
Jul 14 21:28:01 popi kernel: [Firmware Bug]: Duplicate ACPI video bus
devices for the same VGA controller, please try module parameter
"video.allow_duplicates=1"if the current driver doesn't work.
(not tried yet the suggestion...)
Strange thing in /var/log I have many xorg.N.log files.....
[root@ log]# ll Xorg.*
-rw-r--r-- 1 root root 58304 14 lug 21:52 Xorg.0.log
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.0.log.old
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.1.log
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.1.log.old
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.2.log
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.2.log.old
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.3.log
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.3.log.old
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.4.log
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.4.log.old
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.5.log
-rw-r--r-- 1 root root 8515 14 lug 21:25 Xorg.5.log.old
-rw-r--r--. 1 root root 28350 26 giu 14:03 Xorg.9.log
If I try to start with kernel option "nomodeset" I get error about intel
driver and fbdev and vesa ones fail....
Any way to be able to make basic graphic things with this video device in
F13?
Eventually creating Xorg.conf or passing any kernel option at boot time?
At this moment no (EE) in Xorg.0.log and these (WW):
[ 29.975] (II) LoadModule: "intel"
[ 29.975] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 29.976] (II) Module intel: vendor="X.Org Foundation"
[ 29.976] compiled for 1.8.0, module version = 2.11.0
[ 29.976] Module class: X.Org Video Driver
[ 29.976] ABI class: X.Org Video Driver, version 7.0
[ 29.976] (II) LoadModule: "vesa"
[ 29.976] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 29.976] (II) Module vesa: vendor="X.Org Foundation"
[ 29.976] compiled for 1.8.0, module version = 2.3.0
[ 29.976] Module class: X.Org Video Driver
[ 29.976] ABI class: X.Org Video Driver, version 7.0
[ 29.976] (II) LoadModule: "fbdev"
[ 29.976] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 29.976] (II) Module fbdev: vendor="X.Org Foundation"
[ 29.976] compiled for 1.7.99.3, module version = 0.4.1
[ 29.976] ABI class: X.Org Video Driver, version 7.0
[ 29.976] (II) intel: Driver for Intel Integrated Graphics Chipsets:
i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
[ 29.977] (II) VESA: driver for VESA chipsets: vesa
[ 29.977] (II) FBDEV: driver for framebuffer: fbdev
[ 29.977] (++) using VT number 1
[ 29.977] (II) Primary Device is: PCI 00@00:02:0
[ 29.977] (WW) Falling back to old probe method for vesa
[ 29.977] (WW) Falling back to old probe method for fbdev
At the end the intel driver is loaded:
[ 33.260] ABI class: X.Org ANSI C Emulation, version 0.4
[ 33.260] (II) UnloadModule: "vesa"
[ 33.260] (II) Unloading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 33.260] (II) UnloadModule: "fbdev"
[ 33.260] (II) Unloading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 33.260] (II) UnloadModule: "fbdevhw"
[ 33.260] (II) Unloading /usr/lib/xorg/modules/linux/libfbdevhw.so
[ 33.260] (==) Depth 24 pixmap format is 32 bpp
[ 33.260] (II) intel(0): [DRI2] Setup complete
[ 33.260] (II) intel(0): [DRI2] DRI driver: i915
[ 33.260] (**) intel(0): Tiling enabled
[ 33.260] (**) intel(0): SwapBuffers wait enabled
[ 33.260] (==) intel(0): VideoRam: 131072 KB
[ 33.260] (II) intel(0): Attempting memory allocation with tiled buffers.
[ 33.260] (II) intel(0): Tiled allocation successful.
[ 33.261] (II) UXA(0): Driver registered support for the following
operations:
[ 33.261] (II) solid
[ 33.261] (II) copy
[ 33.261] (II) composite (RENDER acceleration)
[ 33.261] (II) put_image
[ 33.261] (==) intel(0): Backing store disabled
[ 33.261] (==) intel(0): Silken mouse enabled
[ 33.261] (II) intel(0): Initializing HW Cursor
[ 33.291] (II) intel(0): RandR 1.2 enabled, ignore the following RandR
disabled message.
[ 33.291] (==) intel(0): DPMS enabled
[ 33.291] (==) intel(0): Intel XvMC decoder disabled
[ 33.292] (II) intel(0): Set up overlay video
[ 33.292] (II) intel(0): direct rendering: DRI2 Enabled
[ 33.292] (--) RandR disabled
...
[ 33.399] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 33.399] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 33.399] (II) AIGLX: enabled GLX_SGI_swap_control and
GLX_MESA_swap_control
[ 33.399] (II) AIGLX: enabled GLX_SGI_make_current_read
[ 33.399] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer
objects
[ 33.400] (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so
[ 33.400] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 33.402] (II) intel(0): Setting screen physical size to 270 x 203
Thanks in advance for your help.
Gianluca
13 years, 11 months
Community gaming Saturday - Session 6 - Wesnoth
by Bruno Wolff III
There will be another Fedora Community Gaming session this weekend.
We will be playing Wesnoth which is a turn based fantasy strategy game.
We will be starting at:
UTC: 1700 Saturday July 17, 2010
EDT: 1pm Saturday July 17, 2010
We need people on time for this one as adding people late is difficult.
We'll meet up in #fedora-games. We'll use the Wesnoth lobby to set up the
game once we see whose playing. Fedora Talk will be available (x2010) for
people that want to try it.
It's not that hard to play for new players.
We'll either play team vs team or team vs AI depending on what people want
to do. We'll play on a small map so we can finish in less than 2 hours. (I'll
move faster this time, I promise.)
We will be using the 1.8 version. People running F12 well need to install
a scratch build (http://koji.fedoraproject.org/koji/taskinfo?taskID=2316236)
or perhaps run an F13 live games image for the session.
A bit more information is at
https://fedoraproject.org/wiki/Community_Gaming#Upcoming_game_sessions
13 years, 11 months
yum update failure
by Gregory P. Ennis
Dear List,
I noticed a problem with an update of evolution on my laptop with
2.6.33.4-95.fc13.i686.PAE. I thought the problem was with evolution
and made an entry on this list. Kevin Fenzi aptly pointed me in the
right direction.
I have done the following :
yum clean all
rm /var/lib/rpm/__db.00*
rpm --rebuilddb
When I try to update an rpm yum is not pulling the recent rpm's from the
repository.
Any ideas?
Greg Ennis
13 years, 11 months
Install questions
by Alex
Hi,
I have just installed FC13 on an AMD Phenom II 1090 six-core box using
the desktop system settings, and I have a few questions. I'm not sure
I like the configuration, and will probably reinstall.
- Is it possible to pass arguments to mkfs during install, so I can
limit the size of the reserved blocks? I have a 1TB disk, and I
believe the default is 5% for ext4, meaning 500MB is wasted.
- If I choose the option during install to use all the available disk
space, it splits it into two partitions, one for root and one for
/home. What is the sense of that for a desktop system? Why not just
create one large partition?
- Power management doesn't work. Instead of the computer going to
sleep, the CPU fan spins very fast, faster than it did even during the
install.
- What is the program that was used to generate the hardware profile
during install? There were quite a few "unknown" entries, and I'd like
to figure out which those were. lspci does not show all the
information that was shown during the install, and all those entries
were pretty well defined. It is running on an Asus Crossfire IV board.
- I have an Sapphire HD5770 video board with 1GB. It's a dual-headed
card. Does the X server support two monitors with this card?
- I have to install Windows 7 on this computer as well. Should I
install Windows 7 first, then install fedora, and use grub as the
bootloader? Will fedora automatically configure the dual-boot if it
detects Windows on the disk already?
- Is USB3.0 supported in fedora? I know the kernel has had it for
quite some time.
Thanks,
Alex
13 years, 11 months
Firefox / Thunderbird setup niggle
by n2xssvv.g02gfr12930
To setup Thunderbird 3 to open Firefox for web links, and Firefox to
open Thunderbird for email links I have to use the default applications
setup provided by Gnome, the KDE one doesn't work. Surely there's got to
be an easier way to do this from KDE! I've not found one yet.
cpp4ever
13 years, 11 months
Issues with SanDisk Sansa 4GB Fuze MP3 Player
by Steven P. Ulrick
Hello Everyone,
I used to have absolutely no problems with this MP3 player. But recently I have
been getting errors when I attempt to add/remove files on this player. If it
matters, I am running the KDE that ships with Fedora 13. This issue started
before the recent KDE updates.
1. "tail -f /var/log/messages" says the following when I plug the player in:
Jul 14 05:35:00 localhost kernel: hub 1-0:1.0: unable to enumerate USB device on
port 1
Jul 14 05:35:02 localhost kernel: usb 1-1: new high speed USB device using
ehci_hcd and address 6
Jul 14 05:35:03 localhost kernel: usb 1-1: New USB device found, idVendor=0781,
idProduct=74c3
Jul 14 05:35:03 localhost kernel: usb 1-1: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
Jul 14 05:35:03 localhost kernel: usb 1-1: Product: SanDisk Sansa Fuze
Jul 14 05:35:03 localhost kernel: usb 1-1: Manufacturer: SanDisk
Jul 14 05:35:03 localhost kernel: usb 1-1: SerialNumber:
7827F0147398B6A80000000000000000
Jul 14 05:35:03 localhost kernel: Initializing USB Mass Storage driver...
Jul 14 05:35:03 localhost kernel: scsi4 : usb-storage 1-1:1.0
Jul 14 05:35:03 localhost kernel: usbcore: registered new interface driver usb-
storage
Jul 14 05:35:03 localhost kernel: USB Mass Storage support registered.
Jul 14 05:35:08 localhost kernel: scsi 4:0:0:0: Direct-Access SanDisk Sansa
Fuze 4GB v02. PQ: 0 ANSI: 0
Jul 14 05:35:08 localhost kernel: scsi 4:0:0:1: Direct-Access SanDisk Sansa
Fuze 4GB v02. PQ: 0 ANSI: 0
Jul 14 05:35:08 localhost kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
Jul 14 05:35:08 localhost kernel: sd 4:0:0:1: Attached scsi generic sg5 type 0
Jul 14 05:35:08 localhost kernel: sd 4:0:0:0: [sdd] 7683072 512-byte logical
blocks: (3.93 GB/3.66 GiB)
Jul 14 05:35:08 localhost kernel: sd 4:0:0:0: [sdd] Write Protect is off
Jul 14 05:35:08 localhost kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write
through
Jul 14 05:35:08 localhost kernel: sd 4:0:0:1: [sde] Attached SCSI removable disk
Jul 14 05:35:08 localhost kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write
through
Jul 14 05:35:08 localhost kernel: sdd:
Jul 14 05:35:08 localhost kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write
through
Jul 14 05:35:08 localhost kernel: sd 4:0:0:0: [sdd] Attached SCSI removable disk
Jul 14 05:35:12 localhost hald: mounted /dev/sdd on behalf of uid 501
2. KDE's "Device Notifier" pops up when I plug the player in:
http://www.afolkey2.net/~steve/SansaFuze-MountingIssue-001.png
3. Then I select "Open with File Manager"
Dolphin shows the Owner of the player as "steve" and the Group as "root"
4. "ls -lh /dev/sdd" shows the permissions of "/dev/sdd" as follows:
[steve@localhost ~]$ ls -lh /dev/sdd
brw-rw---- 1 root disk 8, 48 Jul 14 05:40 /dev/sdd
Also, I AM a member of the group "disk"
5. "/etc/mtab" contains the following line:
/dev/sdd /media/SANSA\040FUZE vfat
rw,nosuid,nodev,uid=501,utf8,shortname=mixed,flush 0 0
6. I am NOT running SELinux...
OK, now the foundation is set. On the the problem.
1. When I try to remove an audio book that I put on the player, I get the
following error message:
http://www.afolkey2.net/~steve/SansaFuze-MountingIssue-002.png
2. Next I will try to remove the files from a terminal. Hopefully I will get
some more useful information:
rm: cannot remove `Jane Austen/Pride & Prejudice/Pride & Prejudice - Chapter 61
- Jane Austen.mp3': Read-only file system
That's odd, since "/etc/mtab" shows "/dev/sdd" as being "rw" Also, "less
/dev/sdd" shows "brw-rw----"
3. The question will arise, "Maybe this is a problem specific to the Audiobook
you are attempting to remove."
"rm -rvf /media/SANSA\ FUZE/MUSIC/Retrospective/" outputs the following:
[steve@localhost ~]$ rm -rvf /media/SANSA\ FUZE/MUSIC/Retrospective/
rm: cannot remove `/media/SANSA FUZE/MUSIC/Retrospective/11 - See See Rider -
The Animals.mp3': Read-only file system
Also, if I attempt to drag a file onto the player in Dolphin, the result is as
follows:
http://www.afolkey2.net/~steve/SansaFuze-MountingIssue-003.png
4. http://www.afolkey2.net/~steve/SansaFuze-MountingIssue-003.png
Almost forgot: if I try to add or remove files to this player as Root, it still
fails. So even Root can't write to this device :)
Again, this player used to work perfectly with Fedora 13. I have not done
anything (knowingly) to cause the problems that I have been having with it...
If you need any more details, let me know.
Steven P. Ulrick
13 years, 11 months
Yumex problem - no network connection
by Thomas Taylor
For some reason Yumex returns an error message saying "Not connected to an
network. Do you want to continue". However Yum works as expected running
updates.
I'm just re-learning Fedora after about five years in other distros and haven't
been able to find the source of this error. ~/.yumex.conf has no referent to a
network. Nothing under /etc/yum (or /yum.repos.d) seems to apply.
Where else should I look? Haven't looked at Fedoras bugzilla yet. Anybody
have a link to that?
Thanks, Tom
--
Tom Taylor - retired penguin
openSuSE 11.3-RC2 x86_64
Fedora 13 x64
KDE 4.4.4, FF 3.6.4
claws-mail 3.7.6
registered linux user 263467
linxt-At-comcast-DoT-net
13 years, 11 months
Help me troubleshoot this problem
by awrobinson-ml@nc.rr.com
I am trying to install Fedora on a PC I built. I had Windows XP running on it for more than a year without any apparent problems. I put a new hard drive in the box and tried Fedora 13 and now Fedora 12. It seems to freeze at random or panic. I suspect hardware or a driver. I've been pulling cards, but it seems to happen regardless of what combination I have in the box. I've tried Gnome, KDE, and now init 3, but it seems to happen with the same frequency. I left it on last night and found these messages on the screen this morning:
[<c0409ab5>] apic_timer_interrupt+0x31/0x38
[drm:drm_fb_helper_panic] *ERROR* panic occurred, switching back to text console
-------------------[ cut here ]--------------
WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x23/0x46()
Hardware name: TF520-A2+06a/0x01
Modules linked in hwmon_vid sunrpc cpufreq_ondemand powernow_k8 ip6t_REJECT nf_conntrack_ipv6 ip5table_filter ip6_tables ipv6 dm_multipath uinput snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer ppdev parport_pc snd parport soundcore r8169 snd_page_alloc i2c_nforce2 k8temp mii ata_generic pata_acpi pata_amd nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core [last uploaded: i2c_dev]
Pid: 1517, comm: abrtd Tainted: G D 2.6.32.14-127.fc12.i686.PAE #1
Call Trace:
[<c04412dd>] warn_slowpath_common
[<c041d044>] ? native_smp_send_reschedule+0x23/0x46
[<c0441306>] warn_slow_path_null+0x12/0x15
[<c041d044>] native_smp_sned_reschedule+0x23/0x46
[<c042dbac>] resched_task_0x5c/0x5f
[<c042dc0d>] check_preempt_curr_idle+0x13/0x15
[<c042c1b1>] check_preempt_curr+0x15/0x18
[<c043d85a>] try_to_wake_up+0x14/0x34
[<c043d915>] default_wake_function+0x14/0x34
[<c042d1e7>] __wake_up_comon_0x39/0x61
[<c0433437>] __wake_up+0x23/0x40
[<c0441a09>] printk_tick+0x37/0x3a
[<c044e8f5>] update_process_times+0x37/0x48
[<c045df9c>] __run_hrtimer_0xa0/0xef
[<c0466dd6>] ? tick_sched_timer_0x0,0xa0
[<c045e1ec>] hrtimer_interrupt_0xe0/0x1d5
[<c041e019>] smp_apic_timer_interrupt_0x68/0x7b
[<c0409ab5>] apic_timer_interrupt_0x31/0x38
[<c07a451c>] ? panic+0xc7/0xe7
[<c07a7056>] oops_end+0x97/0xa6
[<c04273f8>] no_context+0x13b/ox145
[<c04274ee>] __bad_area_nosemaphore+0xec/0xf4
[<c07a7f98>] ? do_page_fault+0x0/0x29f
[<c0427588>] bad_area_nosemaphore+0x13/0x15
[<c07a88c9>] do_page_fault_0x139/0x29f
[<c07a7f98>] ? do_page_fault_0x0/0x29f
[<c07a6693>] error_code+0x73/0x78
[<c044e29b>] ? run_timer_softirq+0xd8/0x1f0
[<c04479ca>] __do_softirq_0xb1/0x157
[<c0447aa6>] do_softirq_0x36/0x41
[<c0447b99>] irq_exit_0x2e/0x61
[<c041e01e>] smp_apic_timer_interrupt+0x6d/0x7b
[<c0409ab5>] apic_timer_interrupt_0x31/0x38
---[ end trace 65e050a46d3d088c ]---
I typed these from the screen, so I cannot swear for the accuracy of every character. I've looked for these type of messages in the message log and the /var/log directory, but haven't found them. I don't see any indications of why it freezes in the message log when it does. I looked for core files in a few places but found none.
I doubt I've given enough info to pinpoint the source of the problem. So my questions revolve around how to troubleshoot this problem. Where would I look for usable information? What experiments could I try that might point to the source of the problem? Would a core file help? If so, how do I get the system to generate one? How do I figure this one out?
Thanks!
Andrew Robinson
13 years, 11 months
evolution 2.30.2-1
by Gregory P. Ennis
Dear List,
When I scanned the fedora archives. it appeared that some have been able
to update to evolution 2.30.2-1. When I run 'yum -y update' after a
'yum clean all' I am still not seeing 30.2-1 in the repositories for
2.6.33.4-95.fc13.i686.PAE.
Have any of you been able to make this update?
Greg Ennis
13 years, 11 months