Allegro.cc - Online Community

Allegro.cc Forums » Off-Topic Ordeals » Gentoo Linux - Kernel Configuration - Modules

This thread is locked; no one can reply to it. rss feed Print
 1   2   3   4 
Gentoo Linux - Kernel Configuration - Modules
Don Freeman
Member #5,110
October 2004
avatar

Yes, make sure that it is indeed pointing to the correct drive.8-)
You can also do this inside the grub menu. press e to edit that line. You will have to fix this in the grub.conf file, but it will at least allow you to boot.:P

--
"Everyone tells me I should forget about you, you don’t deserve me. They’re right, you don’t deserve me, but I deserve you."
"It’s so simple to be wise. Just think of something stupid to say and then don’t say it."

CGamesPlay
Member #2,559
July 2002
avatar

Quote:

I gather that the second suggestion was to verify that (hd1,0) is pointing to my slave (Linux) drive and not my master (Windows) drive? :-/

Yes.

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>

bamccaig
Member #7,536
July 2006
avatar

I said my /etc/fstab said:

/dev/cdrom /mnt/cdrom audo noauto,ro 0 0

audo!? That can't be right! :P I wonder if I did that or if the template came like that...

Marco Radaelli
Member #3,028
December 2002
avatar

This is the relevant part of my grub.conf

title Gentoo kernel-2.6.22-r9
root (hd0,0)
kernel /boot/kernel-2.6.22-r9 root=/dev/sdb3 vga=0x31B video=vesafb:mtrr:3,ywrap,1280x1024-32

I have 2 SATA disks, the one on the first channel has Windows, the one on the second has Gentoo. Go figure why I had to put (hd0,0) in it, but my box kept non-booting until I changed that from (hd1,0) to (hd0,0) ::)

[edit]

Quote:

That can't be right! :P I wonder if I did that or if the template came like that...

Either way that's not preventing your booting process, it's auto BTW ;)

bamccaig
Member #7,536
July 2006
avatar

Marco Radaelli said:

I have 2 SATA disks, the one on the first channel has Windows, the one on the second has Gentoo. Go figure why I had to put (hd0,0) in it, but my bow kept non-booting until I changed that from (hd1,0) to (hd0,0) ::)

Interesting... ??? Thanks. I'll check it out when I get home. Does anybody have an explanation for why grub would interpret them that way?

** EDIT **

I said:

[quote I said my /etc/fstab]/dev/cdrom /mnt/cdrom audo noauto,ro 0 0

audo!? That can't be right! :P I wonder if I did that or if the template came like that...
</quote>
I know you probably thought it was my mistake, but here is /etc/fstab from the current releases/x86/2007.0/stages/stage3-i686-2007.0.tar.bz2 archive on the Tera-byte Dot Com Inc (Canada/http) Gentoo mirror.

1# /etc/fstab: static file system information.
2#
3# noatime turns off atimes for increased performance (atimes normally aren't
4# needed; notail increases performance of ReiserFS (at the expense of storage
5# efficiency). It's safe to drop the noatime options if you want and to
6# switch between notail / tail freely.
7#
8# The root filesystem should have a pass number of either 0 or 1.
9# All other filesystems should have a pass number of 0 or greater than 1.
10#
11# See the manpage fstab(5) for more information.
12#
13 
14# <fs> <mountpoint> <type> <opts> <dump/pass>
15 
16# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
17/dev/BOOT /boot ext2 noauto,noatime 1 2
18/dev/ROOT / ext3 noatime 0 1
19/dev/SWAP none swap sw 0 0
20/dev/cdrom /mnt/cdrom audo noauto,ro 0 0
21#/dev/fd0 /mnt/floppy auto noauto 0 0
22 
23# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
24# POSIX shared memory (shm_open, shm_unlink).
25# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
26# use almost no memory if not populated with files)
27shm /dev/shm tmpfs nodev,nosuid,noexec 0 0

I guess you could consider that a bug worth reporting... :-/

le_y_mistar
Member #8,251
January 2007
avatar

having fun compiling gentoo night after night eh;D

-----------------
I'm hell of an awesome guy :)

bamccaig
Member #7,536
July 2006
avatar

There hasn't actually been a whole lot of compiling thus far... The little bit there has been was fast and pretty. :D

I made the following changes to /boot/grub/grub.conf and reinstalled grub.

1# Which listing to boot as default. 0 is the first, 1 the second, etc.
2default 0
3# How many seconds to wait before the default listing is booted.
4timeout 10
5# Nice, fat splash-image to spice things up. :)
6# Comment out if you don't have a graphics card installed.
7#splashimage=(hd0,0)/grub/splash.xpm.gz
8 
9# ------- Listings: -------
10 
11 
12 
13title=Gentoo Linux 2.6.22-r9
14# Partition where the kernel image (or operating system) is located.
15root (hd0,0)
16kernel /kernel-2.6.22-gentoo-r9 root=/dev/sdb3 dolvm2
17 
18 
19 
20title=Gentoo Linux 2.6.22-r9 (rescue)
21# Partition where the kernel image (or operating system) is located.
22root (hd0,0)
23kernel /kernel-2.6.22-gentoo-r9 root=/dev/sdb3 init=/bin/bb dolvm2
24 
25 
26 
27# The next four lines are only if you dualboot with a Windows system.
28title=Windows XP
29rootnoverify (hd1,0)
30makeactive
31chainloader +1

Note: Emphasis on (hd0,0). I actually added both options for me to test each and the first partition on (hd0) began to successfully boot Linux. Note that I haven't actually attempted to boot my Windows system from this grub install, but I assume it is correct.

From the livecd (hd1) was correct so I stuck with those values when installing grub. Perhaps when booting my slave drive the BIOS switches them or something... :-/

Unfortunately, booting my kernel didn't get too far and eventually the kernel panicked. I'm going to have to recompile the kernel. Hopefully I do it correctly this time... :-/

So how do I determine which modules to build into the kernel and which ones to build as external modules? Should I just go through the entire make menuconfig checking out the help section for each node and guessing? :-/

CGamesPlay
Member #2,559
July 2002
avatar

The easiest way to do it would probably be to go through every menu option and turn all compiled-in modules into external modules. Then, go through and find the options necessary for you to boot, and set those to be compiled-in.

What message did the kernel give you?

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>

Thomas Fjellstrom
Member #476
June 2000
avatar

the panic may not be module related. First I'd make sure the "root=/dev/hdb3" is correct. and try and post the message you get when the kernel panics.

--
Thomas Fjellstrom - [website] - [email] - [Allegro Wiki] - [Allegro TODO]
"If you can't think of a better solution, don't try to make a better solution." -- weapon_S
"The less evidence we have for what we believe is certain, the more violently we defend beliefs against those who don't agree" -- https://twitter.com/neiltyson/status/592870205409353730

Marco Radaelli
Member #3,028
December 2002
avatar

Quote:

There hasn't actually been a whole lot of compiling thus far...

Yeah, starting from a stage3 isn't as cool as from a stage1 :-/

Quote:

The little bit there has been was fast and pretty. :D

That's because you still haven't got X, KDE, OpenOffice, ... ;)

Quote:

So how do I determine which modules to build into the kernel and which ones to build as external modules? Should I just go through the entire make menuconfig checking out the help section for each node and guessing? :-/

Altough that's a good read, I decided to go for the all-in and module-when-needed. So, i.e., my nvidia driver is compiled as a module, because X was complaining it couldn't load it.

CGamesPlay
Member #2,559
July 2002
avatar

Quote:

Altough that's a good read, I decided to go for the all-in and module-when-needed. So, i.e., my nvidia driver is compiled as a module, because X was complaining it couldn't load it.

The reason I wouldn't consider doing this is because if a module has a problem it can't be unloaded, and because I can't change my kernel configuration without rebooting.

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>

bamccaig
Member #7,536
July 2006
avatar

CGamesPlay said:

What message did the kernel give you?

VFS: Cannot open root device "sdb3" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available options:
0300      130528   hda driver:  ide-cdrom
0340     4194302   hdb driver:  ide-cdrom
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

Keep in mind that this was written down and then typed. :)

I have two guesses based on this output: either the kernel doesn't have appropriate support for my SATA hard drives/disc controller (I should note that my PC might also have a RAID controller) or Linux believes the slave drive is actually the master too and I need to indicate /dev/sda3. :-/ I'd guess it's the kernel modules.

Thomas Fjellstrom said:

the panic may not be module related. First I'd make sure the "root=/dev/hdb3" is correct. and try and post the message you get when the kernel panics.

Good call. ;D

Marco Radaelli said:

Yeah, starting from a stage3 isn't as cool as from a stage1 :-/

Now I'm intrigued... The Gentoo Handbook made it seem like stage1 and stage2 was obsoleted. Unfortunately, stage1 and stage2 installations are apparently no longer unsupported... :-/ Once I figure out the stage3 I'll probably attempt a stage2 and stage1. :D

Marco Radaelli said:

That's because you still haven't got X, KDE, OpenOffice, ... ;)

Yeah, I expect a lot more compiling when I actually get a bootable system. I'd be disappointed if there wasn't.

CGamesPlay said:

The reason I wouldn't consider doing this is because if a module has a problem it can't be unloaded, and because I can't change my kernel configuration without rebooting.

Yeah, it sounds a lot better to build as little into the kernel as possible.

CGamesPlay
Member #2,559
July 2002
avatar

Quote:

I have two guesses based on this output: either the kernel doesn't have appropriate support for my SATA hard drives/disc controller (I should note that my PC might also have a RAID controller)

This sounds like the most likely option. If you can't find the right module, giving us the output of lspci will help us identify it.

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>

Thomas Fjellstrom
Member #476
June 2000
avatar

See if your SATA controller is in raid mode, and turn it off. Try "enhanced" and "compatibility" mode, the latter will make the sata disk appear in the spot the first pata disk usually is.

--
Thomas Fjellstrom - [website] - [email] - [Allegro Wiki] - [Allegro TODO]
"If you can't think of a better solution, don't try to make a better solution." -- weapon_S
"The less evidence we have for what we believe is certain, the more violently we defend beliefs against those who don't agree" -- https://twitter.com/neiltyson/status/592870205409353730

bamccaig
Member #7,536
July 2006
avatar

CGamesPlay said:

If you can't find the right module, giving us the output of lspci will help us identify it.

1(chroot) livecd / # lspci
200:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 81)
300:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port (rev 81)
400:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
500:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
600:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
700:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
800:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
900:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
1000:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
1100:1f.0 ISA bridge: Intel Corporation 82801GH (ICH7DH) LPC Interface Bridge (rev 01)
1200:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
1300:1f.2 RAID bus controller: Intel Corporation 82801GR/GH (ICH7 Family) SATA RAID Controller (rev 01)
1400:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
1501:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 LE] (rev a1)
1602:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev c0)
1702:03.0 Ethernet controller: Atheros Communications, Inc. AR5006X 802.11abg NIC (rev 01)
1802:04.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
1902:05.0 Communication controller: Agere Systems Unknown device 0620
2002:08.0 Ethernet controller: Intel Corporation 82801G (ICH7 Family) LAN Controller (rev 01)

Thomas Fjellstrom said:

See if your SATA controller is in raid mode, and turn it off.

The hard drives are not actually actively using RAID, but both drives' SATA mode is set to RAID... I read that it is the recommended setting regardless of whether you're actually using RAID or not for whatever reason... :-/ I don't know.

CGamesPlay
Member #2,559
July 2002
avatar

I have the same SATA controller. Verify that "Intel PIIX/ICH SATA support" is compiled in. You can find it in Device Drivers -> Serial ATA (prod) and Parallel ATA (experimental) drivers (kernel source 2.6.19-gentoo-r5).

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>

Thomas Fjellstrom
Member #476
June 2000
avatar

Quote:

The hard drives are not actually actively using RAID, but both drives' SATA mode is set to RAID... I read that it is the recommended setting regardless of whether you're actually using RAID or not for whatever reason... :-/ I don't know.

I call bunk. ;) I don't see why it'd be recommended.

I have a ICH9 version of that chip, and have the following modules loaded:

ata_generic             9988  0
ata_piix               20996  9

both are in the initramfs/initrd that "update-initramfs" generated (debian script).

in fact, everything is set to module..

moose@natasha:~/data/Anime$ lsmod
Module                  Size  Used by
snd_rtctimer            5216  0
binfmt_misc            14860  1
coretemp                9856  0
w83627ehf              24464  0
i2c_isa                 6400  1 w83627ehf
i2c_dev                10248  0
i2c_i801               11036  0
cpuid                   5768  0
isofs                  39268  0
udf                    90024  1
nfs                   272728  2
lockd                  76336  2 nfs
sunrpc                198536  3 nfs,lockd
rfcomm                 47656  2
l2cap                  28672  11 rfcomm
bluetooth              63876  4 rfcomm,l2cap
vboxdrv              1649696  0
ppdev                  11272  0
acpi_cpufreq           10632  0
cpufreq_stats           8160  0
cpufreq_ondemand       10896  4
cpufreq_userspace       6048  0
cpufreq_conservative     9608  0
freq_table              6464  3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_powersave       3072  0
button                 10400  0
sbs                    21520  0
ac                      7304  0
dock                   12264  0
container               6400  0
video                  21140  0
battery                12424  0
tun                    14080  0
af_packet              28172  2
bridge                 64168  0
ipv6                  317192  14
parport_pc             41896  0
lp                     15048  0
parport                44172  3 ppdev,parport_pc,lp
snd_hda_intel         337192  2
snd_pcm_oss            50048  0
snd_mixer_oss          20096  1 snd_pcm_oss
snd_pcm                94344  2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy           5380  0
snd_seq_oss            36864  0
snd_seq_midi           11008  0
snd_rawmidi            29824  1 snd_seq_midi
snd_seq_midi_event      9984  2 snd_seq_oss,snd_seq_midi
snd_seq                62496  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
nvidia               7013492  24
xpad                   11400  0
atl1                   40204  0
lirc_atiusb            21552  1
lirc_dev               18248  1 lirc_atiusb
mii                     7424  1 atl1
snd_timer              27272  3 snd_rtctimer,snd_pcm,snd_seq
i2c_core               30208  5 w83627ehf,i2c_isa,i2c_dev,i2c_i801,nvidia
snd_seq_device         10260  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd                    69288  13 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
psmouse                45596  0
soundcore              10272  1 snd
shpchp                 38300  0
pci_hotplug            36612  1 shpchp
snd_page_alloc         12560  2 snd_hda_intel,snd_pcm
serio_raw               9092  0
pcspkr                  4608  0
intel_agp              30624  0
evdev                  13056  3
usbhid                 32576  0
hid                    33408  1 usbhid
ext3                  146576  4
jbd                    69360  1 ext3
mbcache                11272  1 ext3
sg                     41384  0
sd_mod                 32512  8
sr_mod                 19876  1
cdrom                  41768  1 sr_mod
ata_generic             9988  0
ata_piix               20996  9
libata                138928  2 ata_generic,ata_piix
scsi_mod              172856  4 sg,sd_mod,sr_mod,libata
ehci_hcd               40076  0
uhci_hcd               29600  0
usbcore               161584  6 xpad,lirc_atiusb,usbhid,ehci_hcd,uhci_hcd
thermal                16528  0
processor              36232  2 acpi_cpufreq,thermal
fan                     6920  0
fuse                   52528  5
apparmor               47008  0
commoncap               9472  1 apparmor

--
Thomas Fjellstrom - [website] - [email] - [Allegro Wiki] - [Allegro TODO]
"If you can't think of a better solution, don't try to make a better solution." -- weapon_S
"The less evidence we have for what we believe is certain, the more violently we defend beliefs against those who don't agree" -- https://twitter.com/neiltyson/status/592870205409353730

BAF
Member #2,981
December 2002
avatar

I wouldn't go changing your RAID settings at this point, or it's going to fuck with your Windows install. At this point, I assume you had to install Windows with a RAID driver. Turning off RAID will likely make windows throw a blue screen pretty quickly on boot.

Just make sure you have the right drivers compiled IN to your kernel for the controller, and if anything is required for LVM to work, make sure that is compiled in as well. Remember, unless you mess around with initrd's and stuff, your kernel needs to be able to access your drives without loading any modules.

Thomas Fjellstrom
Member #476
June 2000
avatar

Quote:

Just make sure you have the right drivers compiled IN to your kernel for the controller, and if anything is required for LVM to work, make sure that is compiled in as well.

Don't need to. My servers run off LVM and/or MD raid (root as well), and they are all enabled as modules.

Thats the joy of initramfs, you just generate a new one, and wham, all the modules you need are loaded before linux even attempts to init the real root filesystem.

--
Thomas Fjellstrom - [website] - [email] - [Allegro Wiki] - [Allegro TODO]
"If you can't think of a better solution, don't try to make a better solution." -- weapon_S
"The less evidence we have for what we believe is certain, the more violently we defend beliefs against those who don't agree" -- https://twitter.com/neiltyson/status/592870205409353730

BAF
Member #2,981
December 2002
avatar

Thats why I said:

Remember, unless you mess around with initrd's and stuff, your kernel needs to be able to access your drives without loading any modules.

:P

Don Freeman
Member #5,110
October 2004
avatar

Quote:

Interesting... ??? Thanks. I'll check it out when I get home. Does anybody have an explanation for why grub would interpret them that way?

Are you even listening to me?!?:o I am trying to help you out...:P Read my post about the file: /boot/grub/device.map
This is also in the Gentoo handbook, in the section about installing grub.::) Also, when in the grub menu on boot, you can hand edit each line. You can use tab completion (limited, and sorta retarded...but doable) to find out what drive hd0 or hd1 is pointing to and what files are in the boot directory (actually where grub was installed).8-)

Quote:

CGamesPlay said:
If you can't find the right module, giving us the output of lspci will help us identify it.

I believe I have said this in the beginning.:o It would be nice if you showed us the output of lsmod with the gentoo cd kernel running. That way you can get an idea of what modules you will need.:P

I am willing to help you, but if you are not going to listen, then I am not going to bother...:-/

With the kernel panic, it sounds as though it could not find the root drive. Most likely cause: invalid SATA controller module, or you are using an IDE controller module with causes your root to actually be /dev/hdb3 instead of /dev/sdb3::) There have been multiple references above about people with that same chipset, so use there SATA module. For something like the drive controller module, if that module fails...what else are you going to do? Compile that into the kernel.:P

--
"Everyone tells me I should forget about you, you don’t deserve me. They’re right, you don’t deserve me, but I deserve you."
"It’s so simple to be wise. Just think of something stupid to say and then don’t say it."

Marco Radaelli
Member #3,028
December 2002
avatar

bamccaig said:

Now I'm intrigued... The Gentoo Handbook made it seem like stage1 and stage2 was obsoleted. Unfortunately, stage1 and stage2 installations are apparently no longer unsupported... :-/ Once I figure out the stage3 I'll probably attempt a stage2 and stage1. :D

Well, do not do it unless you like watching tons of compilation lines flow through the screen (like me ;D), because IIRC a stage1 implies compiling the whole toolchain (I guess that's the right name).

Don Freeman said:

Read my post about the file: /boot/grub/device.map

Not to fight you, but:

device.map

(fd0)   /dev/fd0
(hd0)   /dev/sda
(hd1)   /dev/sdb

mount output

/dev/sdb3 on / type reiserfs (rw,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw,nosuid,noexec)
/dev/sdb6 on /mnt/fat32 type vfat (rw,noexec,nosuid,nodev,noatime)
/dev/sda1 on /mnt/winxp type ntfs (ro,noatime,umask=0022)
/dev/sdb5 on /mnt/winxp-share type ntfs (ro,noatime,umask=0022)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
/dev/sdb1 on /boot type ext2 (rw,sync,noatime)

grub.conf

title Gentoo kernel-2.6.22-r9
root (hd0,0)
kernel /boot/kernel-2.6.22-r9 root=/dev/sdb3 vga=0x31B video=vesafb:mtrr:3,ywrap,1280x1024-32

HoHo
Member #4,534
April 2004
avatar

Going with stage1 will only mean you'll need to compile GCC, glibc, stdlibc++-v3, binutils and a few other packages. It doesn't take all that much time, actually. Though I haven't used the official handbook for ages, I usually just get some of the "experimental" guides from Gentoo forum. They mostly go with stage3 base but compile toolchain anyway to make sure that system is as stable as possible.

When making the first Gentoo install I wouldn't bother with anythinb tut stage 3. Get something to work and work on from there.

__________
In theory, there is no difference between theory and practice. But, in practice, there is - Jan L.A. van de Snepscheut
MMORPG's...Many Men Online Role Playing Girls - Radagar
"Is Java REALLY slower? Does STL really bloat your exes? Find out with your friendly host, HoHo, and his benchmarking machine!" - Jakub Wasilewski

Don Freeman
Member #5,110
October 2004
avatar

Quote:

VFS: Cannot open root device "sdb3" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available options:
0300 130528 hda driver: ide-cdrom
0340 4194302 hdb driver: ide-cdrom
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

It is as I feared. Your kernel is compiled with the IDE modules...NOT your SATA modules.::) Also, are you using hd0,1 or hd1,0 for the root in your /boot/grub/grub.conf file?
This should be something like:

root (hd1,0)      //really /dev/sdb1, partition 1.
// If you installed boot on your third partition... use root (hd1,2) (3-1=2)
kernel /vmlinuz-2.6.22-gentoo-r2 root=/dev/sdb3 //set root= to your actual / directory

You can also use the new style ATA modules for your IDE CDROM drives as well...they would become: /dev/sr0 and /dev/sr1. I believe that the major push is towards this anyway, as quite a few distros are doing this. You may experience problems running both subsystems (the new style ATA and the old style).

Also, make sure you compiled in support for the filesystem you are using. If you did not compile in support for reiserfs and you are using reiserfs as your filesystem...well, no wonder it doesn't work!::)

I believe there have been a couple of people here that said they had that same chipset. Just find those in your kernel's menuconfig and make sure they are being compiled in.::)

Quote:

Not to fight you, but:

device.map

(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/sdb

Actually, you can change that file to say whatever you want after...but if you don't do the grub setup again...it does not take effect!:P

--
"Everyone tells me I should forget about you, you don’t deserve me. They’re right, you don’t deserve me, but I deserve you."
"It’s so simple to be wise. Just think of something stupid to say and then don’t say it."

Marco Radaelli
Member #3,028
December 2002
avatar

Quote:

Actually, you can change that file to say whatever you want after...but if you don't do the grub setup again...it does not take effect!

A-ha! I didn't know ;D

 1   2   3   4 


Go to: