Gentoo…Argh!!
This might be a short blog entry but it’s due to the fact that I’m posting from links while attempting to install Gentoo. I have tried to boot into Gentoo but I keep getting an error where it’s detecting USB ports and then fails. It is successful with the first 2 ports but then hangs. Also, while booting, it says that I’m using the ext3 filesystem for root but I am using Reiser. I have edited /etc/fstab to have reiserfs as root but it doesn’t seem to recognize it. Anybody have ideas why this is happening? (Peter, Derek, other Gentoo users?) I started from the Stage 1 tarball and installation went smoothly so I’m confused as to why I am getting this problem.
Perhaps you could post/send your /etc/fstab? And a dump of the errors on boot would be useful, but I’m not sure where that file would be kept.
Comment by peter — October 5, 2003 @ 11:21 pmDoes it write it out to a system log? I know on OS X, all the startup stuff gets written to /var/log/system.log… both good and bad stuff. I would assume it would be the same, as “dmesg” would have to get its information from somewhere…
You may also want to try plugging something else into the other USB ports… I’m assuming the first two are occupied by the KB and Mouse, so it wouldn’t hurt to plug another mouse or something in there to see if that’s the problem.
As for the ext3 vs. Reiser thing, the only thing I can think to suggest may sound a little silly, but it caught me a couple times… make sure when you’re booted from the CD you’re not editing /etc/fstab, because that edits the one loaded into ram… mount your hard-drive, and edit that fstab (/mountpoint/etc/fstab) to make sure your edits stick. Maybe not the most brilliant thing I could have said, but sometimes it doesn’t hurt to state the obvious.
“My printer won’t print!”
“Is it plugged in?”
“Uh, no.”
You don’t know how many times I’ve had that exact conversation.
Comment by Andrew — October 6, 2003 @ 12:37 amAlso, its either root or boot that needs the notail flag appended in the /etc/fstab file if you use RFS systems. I’m not sure which one, but it never hurts to double check
As far as it not detecting USB ports though, the same thing happened to tyler. turns out he hadnt emerged hotplug.. But if you’s detects the first two, thats probably not it.
But I echo andrews advice, make sure you are editing the right file
Comment by Derek — October 6, 2003 @ 2:16 amHere is my /etc/fstab:
/dev/hda1 /boot ext3 noauto,noatime 1 1
/dev/hda3 / reiserfs noatime,notail 0 0
/dev/hda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
/dev/cdroms/cdrom1 /mnt/cdrom2 iso9660 noauto,ro 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
I couldn’t find a log of the errors, but here is a sample of what I’m getting:
Beginning storage detection
Comment by Trevor — October 6, 2003 @ 9:05 am.
.
.
.
.
usb.c: registered new driver hub
Detected usbcore hardware
.
.
.
usb.c: new USB bus registered, assigned bus number 1
ehci-hcd.c: USB 2.0 support enabled, EHCI rev 1. 0
hub.c: USB hub found
hub.c: 6 ports detected
Detected ehci-hcd hardware
Scanning for uhci…uhci.c: USB Universal Host Controller Interface driver v1.1
.
.
usb.c: new USB bus regisreted, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
usb-ohci.c: USB OHCI at membase 0xe09b8000, IRQ 11
usb-ohci.c: usb-00:02.1, PCI device 10de:0067 (nVidia Corporation)
usb.c: new USB bus registered, assigned bus number 3
(this is where it freezes)
Hmm… I’d be interested to see what comes AFTER the USB is recognized… It looks like the USB stuff gets done ok, so you may want to try and see what gets initialized after it to see if that’s what’s hanging it.
And since when did nVidia do anything USB?
Comment by Andrew — October 6, 2003 @ 9:39 amyou might also want to look at these posts on the gentoo forums:
http://forums.gentoo.org/viewtopic.php?t=76771&highlight=gigabyte+motherboard
http://forums.gentoo.org/viewtopic.php?t=58695&highlight=gigabyte+motherboard
Comment by Andrew — October 6, 2003 @ 9:53 amI’m with Andrew — I looks like USB went fine and it’s the next step that’s causing the problem.
And NVidia makes nforce2 chipsets on motherboards.
Comment by peter — October 6, 2003 @ 2:04 pm