On Tuesday 20 February 2007, Basil Chupin wrote: [...] > Hi Lee, > > I would be happier if someone could confirm your logic on this - > nobody seems to have even read your post (and your follow-up). > > Yesterday I upgraded my 10.2 installation to 10.3 Alpha1 which, as > you may know, has the 2.6.20 kernel. I also did a new, clean, install > of Alpha1. Neither of these seem to support your findings. > > The new, clean install is particularly worrying because it departs > totally from what I am used to when it comes to identifying drives. > For example, the fstab which was generated by the clean install shows > this: > > dev/disk/by-id/ata-QUANTUM_FIREBALLlct20_20_552102678031-part1 / ext3 > acl,user_xattr 1 1 > /dev/disk/by-id/ata-QUANTUM_FIREBALLlct20_20_552102678031-part2 swap > swap defaults 0 0 > /dev/disk/by-id/ata-QUANTUM_FIREBALLlct20_20_052117040222-part5 swap > swap defaults 0 0 > proc /proc proc defaults 0 0 > sysfs /sys sysfs noauto 0 0 > debugfs /sys/kernel/debug debugfs noauto 0 0 > usbfs /proc/bus/usb usbfs noauto 0 0 > devpts /dev/pts devpts mode=0620,gid=5 0 0 > /dev/fd0 /media/floppy auto noauto,user,sync 0 0 > > Nowhere is there a hdx or sdx appearing. The sudden appearance of > device ID number is a bit worrying (seeing as how MS is not on the > scene). > > When I UPGRADED an existing 10.2 installation, 10.3 Alpha with its > 2.6.20 kernel had no troubles in working with the old hdx naming > convention and the fstab was left untouched. > > HOWEVER, in both instances there was one weird anomaly: in the > Control Centre under Hardware the IDE DMA MODE there were NO entries. > This list is totally BLANK in both cases as if no devices are > present. > > Something somewhere is not kosher. > > Cheers. ==============
Hi Basil, Your info adds even more questions to the whole thing. I know the way Suse usually attacks things in the fstab now are such that many things don't even appear in it any longer. The optical drives are not shown until they are mounted by the system and then by some "id" number in the "My Computer" icon, so I am not sure how the .20 kernel plays into their scheme. As I mentioned, the SATA drives won't be affected, but many of the optical devices are still PATA, which used the hdXX tags and I don't see any hdXX listings in your above fstab either. Check your Grub menu.lst to see what it has. Instructions I have read on the .19 & .20 kernels elsewhere and with other distributions are where I got my info. In talking with some other users, they seem to confirm these findings. The libata module is of course not new, as I originally thought, but it certainly seems like some other things have changed. I also want to comment about the srX designation. I happened to be looking thru some old notes in early Suse versions and found an old /etc/fstab printout. Guess what? It had sr1 & sr0 designated for the /dev/cdrom & /dev/cdwriter. I thought I remembered something like that earlier. :-) Did you check your /dev directory to see if there were some srX devices there in your 10.3 setup? They may not even appear there or be needed now with the automatic mounting system in place? Maybe some kind Suse kernel maintainer will weigh in on the discussion. regards, Lee -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
