Using the proposed solution in the release notes
(pci=off idel=0x180,0x386), leads to the following
error message: "EIP is at pci_read 0x1a/0x21 ...
Kernel panic: Attempted to kill init"
Pentium 4HT 3.0GHz
Motherboard: ASUS P4C800
HD: Maxtor DiamondMax Plus9 160GB SATA
DVD: LG GSA-4040B
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
I have FC2 (no updates - just the 4 cd from the site)
and I try to make xconfig
whell a window pops up and instead of getting readable information, I get
small circles (instead of characters) with various parts filled in black
(half, full, quarter.. no circles just spaces....etc)
I have English US and English language only as system wide and during the
Date: Fri, 28 May 2004 13:26:31 -0400
From: Alan Cox <alan(a)redhat.com>
Subject: Re: kernel 2.6.6
To: For testers of Fedora Core development releases
Content-Type: text/plain; charset=us-ascii
On Fri, May 28, 2004 at 10:02:40AM -0400, Mike Lurk wrote:
> So far with this kernel (2.6.6-1.391) I haven't been able to do
> in openGL. As a matter of fact any of the 2.6.6 kernels haven't worked
> with openGL. The mobo is an Intel with a p3 600 and an integrated I810
> video and the intel sound integrated as well. Any help would be
Try the i586 kernel instead of the i686 one. If that works then
in the 4G/4G support has probably been broken again. Either way please
us know what happens
The i586 kernel worked. I tried to recompile with 4G/4G turned off but
during the recompile it wouldn't create the custom kernel directory
The latest vnc server package, vnc-server-4.0-1.beta5.4, is missing
the vnc.so module. Should this be filed as a separate bug, or as a
comment added to
Senior System Administrator
Red Hat Certified Engineer / Local Linux Lobbyist
Ever see a penguin fly? -- Try Linux.
GPL all the way: Sell services, don't lease secrets
Ok, have the drivers installed via README from
http://www.ic.unicamp.br/~oliva/snapshots/FC2-firewire/0README Section 2.1
However, rebooting this kernel 2.6.6-1.403 and running modprobe ohci1394
and sbp2 (mind you it's detected at kernel boot), and
running sh ./rescan-scsi-bus.sh changes absolutely nothing. My external
Firewire BUSLink 48x12x48 drive is still not detected.
sbp2 18184 0
ohci1394 26392 0
ieee1394 278964 2 sbp2,ohci1394
and lspci -v shows:
02:09.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394
Controller (Link) (prog-if 10 [OHCI])
Subsystem: Procomp Informatics Ltd: Unknown device 8010
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at feafb800 (32-bit, non-prefetchable)
Memory at feaf4000 (32-bit, non-prefetchable) [size=16K]
Capabilities:  Power Management version 1
However I can go back to my good old kernel 2.6.1-1.65smp and my
Firewire drive is detected under Xcdroast-0.98alpha15-2 and works even. :)
I'm afraid we're still looking for some patch upstream maybe by kernel
2.6.7 or 2.6.8 or something like 2.7 or maybe never :)
Your archive firewire-dd.bz2.tar doesn't expand given your instructions
in section 2 of your README. tar -xzf firewire-dd.tar.bz2 yields:
tar (child): firewire-dd.tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
Any work around?
Recieved journal commit failure running 2.6.6-1.381
System now fails to boot "mkrootdev: label / not found".
Can get further into the boot process using "kernel /vmlinuz-2.6.6-1.381
ro root=/dev/hda5 rhgb quiet" but this only gets me to :
EXT3-fs: hda7: couldn't mount because of unsupported optional features
(1000100)." <- not sure what they might be.
mount: error 22 mounting ext3
I have been trying to get into rescue mode via network (ftp/nfs) but
anaconda responds with:
Running anaconda, the Fedora Core rescue mode - please wait...
File "/usr/bin/anaconda", line 913
xsetup_failed = xserver.startXServer(videohw, monitorhw, mousehw, kbd,
IndentationError: unindent does not match any other indentation level
install exited abnormally
Is their a way I can get this system back to get a better look at logs
etc. Where should I be looking for recovery doco etc.
Cheers in advance
As promised, the first Fedora Core 2 based tree of Aurora SPARC Linux is
now available. Like I've previously said, its not an installable tree
(this means, no ISOs). We'll get there eventually, this is just
something so that people can get a baseline upgrade.
Now, I have yumified the tree, so if you're feeling really brave, you
can always point yum at it, and try to upgrade that way. A version of
yum for Aurora 1.0 is here:
If you're a listed mirror site, please sync the build-1.91 directory,
and chime in. The primary directory is currently at:
Now, for the known bugs:
After tearing my hair out for a week or so, I came to the conclusion
(backed by several other people trying to do the same thing for other
distributions) that SILO 1.4.* is completely broken. Build 1.91 uses
SILO 1.3.2 which should work fine. If it doesn't, let me know.
The sparc32 kernel in the tree has known issues with sun4c. If you're
interested in helping to troubleshoot these issues, email me offlist,
otherwise, be forewarned. :)
system-config-display doesn't work right. Me and Peter fixed it
yesterday, though, so there's no need to file bugs on it.
I know the package revisions don't quite match up to FC2 final. Next
tree should be a lot closer.
Any other bugs that you find? Please either email me or file them in
bugzilla.auroralinux.org, under Corona.
Thanks for your continued patience,
Tom "spot" Callaway <tcallawa(a)redhat*com> LCA, RHCE
Red Hat Sales Engineer || Aurora SPARC Linux Project Leader
"If you are going through hell, keep going."
- Sir Winston Churchill
Date: Sun, 30 May 2004 13:29:50 -0500
From: Law Horne <zimhat(a)foou.net>
Subject: kernel 2.6.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I have had trouble getting the 2.6.6 kernels from Arjan's repo to work
with my nic. I'm useing the nforce2 ethernet controller. I have even
tried the latest(403) out of Arjan's repo. And it worked the first
I thought I was safe but ever boot after that it cannot ping my
I have not had a problem with the 2.6.5 kernels at all. I'm not sure
what to do to trouble shoot this. And it does not appear that anyone
else is having the same problem. I have posted my boot log before but
did not get a response. If someone could point me in the direction of
what might be needed to resolve this issue I would appreciate it.
I have had the same problem with the nforce based motherboards. The one
thing that I tried was to turn off kudzu and it seems to work. I can
connect to the internet and the internal network.