LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-06-2010, 11:36 PM   #1
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,912

Rep: Reputation: Disabled
Post 13.0 switch from hd* --> sd* in -current with 2.6.32+


I suspect a few people will eventually run into this problem, and while it's easy to get around for the more experienced users (the ones that *should* be running -current), we all know that everyone isn't in that group :-)

http://rlworkman.net/howtos/libata-switchover
 
Old 01-07-2010, 01:22 AM   #2
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
I'm not sure this is needed, but to play it safe (even tho the release notes didn't mention it), before I did the upgrade was to delete the file:

/etc/udev/rules.d/70-persistent-cd.rules

Then did the upgrade, my reboot, and the rule gets recreated.

Again, I'm not sure if that's needed but I really didn't want to have cdrom/dvdrom drive issues.

As you can see below, the ID_PATH changes, from -ide to -scsi

FWIW, I diff'd the files and they do indeed show a difference:

-sanitized

Quote:
-# PLEXTOR_DVDR_PX-XXXX (pci-0000:00:09.0-ide-1:0)
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdrom0", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdr0", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdr", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdwriter0", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdwriter", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdrw0", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="writer", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="dvd0", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="dvd", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="dvdrw0", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="dvdwriter0", ENV{GENERATED}="1"
-ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-ide-1:0", SYMLINK+="dvdwriter", ENV{GENERATED}="1"
+# DVDR_PX-XXXX (pci-0000:00:09.0-scsi-1:0:0:0)
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdrom0", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdr0", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdr", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdwriter0", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdwriter", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdrw0", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="writer", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="dvd0", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="dvdrw0", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="dvdwriter0", ENV{GENERATED}="1"
+ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:09.0-scsi-1:0:0:0", SYMLINK+="dvdwriter", ENV{GENERATED}="1"
I'm not sure if I should send this off to Mr. V or not (tho he may read this dunno.

Offtopic: wow preempt kernel, tickless timer too now in new kernel, very nice, I don't have to rebuild it anymore It's working great on acer aspire one netbook (now has thermal info (acerhdf) woohoo! and my asus desktop.

-Fogie
 
1 members found this post helpful.
Old 01-07-2010, 01:36 AM   #3
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,912

Original Poster
Rep: Reputation: Disabled
Yes, good catch re the persistent optical device rules file - that will need to be killed before the reboot.
I just cleaned up the howto quite a bit (thanks to mrgoblin) and added a tip about using an initrd (thanks to goblin again).
 
Old 01-08-2010, 07:13 AM   #4
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 14.1 32bit
Posts: 719
Blog Entries: 3

Rep: Reputation: 76
Hello Robby,

I upgraded my -current machine using your HOW-TO. Thank you.

I don't know if this is self-evident but I went through an issue to identify how my /dev/hdd2 Slackware partition would be renamed. At first, I thought I just needed to rename /dev/hdd2 into /dev/sdd2 but it didn't work because my hardware is organized like this:

Quote:
/dev/hda: Hard disk
/dev/hdb: Hard disk
/dev/hdc: DVD driver
/dev/hdd: Hard disk (with Slackware)
With new kernel, the renaming was:

Quote:
/dev/sda: Hard disk => /dev/sda
/dev/hdb: Hard disk => /dev/sdb
/dev/hdc: DVD driver => /dev/sr0
/dev/hdd: Hard disk (with Slackware) => /dev/sdc
I assume /dev/sd* only list hard disks.

Maybe a mention on this topic might be useful in the notes of next Slackware version and in your HOW-TO.
 
Old 01-08-2010, 08:11 AM   #5
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,912

Original Poster
Rep: Reputation: Disabled
Thanks; I added a note about this to the howto.
 
Old 01-08-2010, 08:43 AM   #6
GazL
Senior Member
 
Registered: May 2008
Posts: 3,319

Rep: Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881
Robby I'm confused. If you don't run /sbin/lilo at step 2 to update its map file, then how is the bootloader going to load the the new kernel at step 5 when you reboot? Won't it just load the old kernel (assuming the sectors on disk haven't been overwritten in the meantime), but then, if it uses the old kernel, won't it also use the old names too, leaving you in the same situation as you were?

I can see how this process would work if you were rebooting using an install cd with the new kernel on it and specifying root= to get at your rootfs in order to run /sbin/lilo under the new kernel version but the howto doesn't mention anything about booting from cd. Am I missing something here?

PS. This is just for the purpose of my understanding. My system already uses sd* names so I don't have to go through this process in anger.

Last edited by GazL; 01-08-2010 at 08:45 AM.
 
Old 01-08-2010, 09:20 AM   #7
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 14.1 32bit
Posts: 719
Blog Entries: 3

Rep: Reputation: 76
Quote:
Originally Posted by GazL View Post
Robby I'm confused. If you don't run /sbin/lilo at step 2 to update its map file, then how is the bootloader going to load the the new kernel at step 5 when you reboot? Won't it just load the old kernel (assuming the sectors on disk haven't been overwritten in the meantime), but then, if it uses the old kernel, won't it also use the old names too, leaving you in the same situation as you were?
I may have got into such a situation. After the first reboot (lilo was not run), the system hanged at the step before "BIOS Check Successful" message appears (i.e. the dots appeared and then nothing). I used a CD -current from July (i.e. pre-13.0) to boot and tinker with the various settings (lilo.conf, fstab, initrd.gz).

At one point, I ran lilo and on the next reboot, I went farther (i.e after "BIOS Check Successful") until I tripped again (on my initrd.gz image). Finally I found my issue (ie. /dev/hdd2 being renamed into /dev/sdc2).
 
Old 01-08-2010, 09:33 AM   #8
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,912

Original Poster
Rep: Reputation: Disabled
You're exactly right. Fixed.
I knew what I meant, but I didn't at all *write* what I meant. I was intending that to mean "don't try to run lilo with the s/hda/sda/ changes" yet.
 
Old 01-08-2010, 09:52 AM   #9
GazL
Senior Member
 
Registered: May 2008
Posts: 3,319

Rep: Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881
Quote:
Originally Posted by rworkman View Post
You're exactly right. Fixed.
I knew what I meant, but I didn't at all *write* what I meant. I was intending that to mean "don't try to run lilo with the s/hda/sda/ changes" yet.
Much better.
 
Old 01-08-2010, 11:37 AM   #10
Toods
Member
 
Registered: Dec 2005
Location: UK
Distribution: Slackware 12.1
Posts: 249

Rep: Reputation: 32
Quote:
Originally Posted by rworkman View Post
I suspect a few people will eventually run into this problem, and while it's easy to get around for the more experienced users (the ones that *should* be running -current), we all know that everyone isn't in that group :-)

http://rlworkman.net/howtos/libata-switchover
Robby, would it be possible for you to write a similar HOWTO for those using GRUB (Legacy)?. I tried to figure this out myself but there are a few differences such as how drives are numbered and I am not sure.

Thanks,

Bill.
 
Old 01-08-2010, 03:27 PM   #11
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,912

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Toods View Post
Robby, would it be possible for you to write a similar HOWTO for those using GRUB (Legacy)?. I tried to figure this out myself but there are a few differences such as how drives are numbered and I am not sure.
I've never used grub, believe it or not, so it would be better if someone else wrote that up. I'll be more than happy to include a link to it.
 
Old 01-09-2010, 03:31 AM   #12
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
I've got debian lenny and slack --current on one box together. Debian's grub controls the boot loader. For their grub all I had to do was change the hda to sda, fwiw. As far as slackware's grub I don't use it on --current, so I've got no pointers to mention.
 
Old 01-09-2010, 05:43 AM   #13
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 14.1 32bit
Posts: 719
Blog Entries: 3

Rep: Reputation: 76
@rworkman

Back to your HOWTO. I think that lilo (step 2) should be run as a last step just before reboot (step 4) because if one uses initrd.gz image a rerun of lilo is necessary.
 
Old 01-09-2010, 07:25 AM   #14
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 237

Rep: Reputation: 58
Thanks! Was wondering my other drive wouldn't mount. I had both sda and hda used previously. I used dmesg and also guessed at the naming convention, as you suggested, and settled on the naming in fstab from hda2 to sdb2. Works now.
 
Old 01-09-2010, 09:18 AM   #15
wroom
Member
 
Registered: Dec 2009
Location: Sweden
Posts: 83

Rep: Reputation: 24
Wow.

I am tinkering with a HD recovery tool, and am having enough trouble already with treating different devices correctly. Identifying the unit as an IDE drive and using the correct control method on the device, (not treating it as a scsi), will be even more difficult to do in a safe manner if the device name and major/minor numbers get obfuscated just because of pedantery in naming the drives. An IDE disk is an IDE disk, and a SCSI-disk is a SCSI disk, even for the SATAs.
Low level I/O in Linux has become very much to complicated as it is already, without introducing any confusing renaming of devices.

Thing is, if the device is a SCSI disk, firewire disk, USB, SATA or alike, then the device will be an "SD" anyhow. Why not letting the IDE interface be left as it is, since it is currently working, and is at the end of its life cycle? If one wants an "SD" entry for an IDE device, this has been possible for a long time now in Linux.

Is this yet another example of people meddling with things they shouldn't touch, with no other obvious reason than to feed the "symmetry devil"? Or am i missing something important? Is there a particularly good reason to start naming the old ide devices as scsi?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
When I switch from windows XP to Xubuntu will I be able to keep my current e-mail? Mac_09 Linux - General 2 05-11-2008 08:33 PM
Suggestion: Minimum post count to post in old inactive threads Eternal_Newbie LQ Suggestions & Feedback 5 04-28-2008 09:34 AM
Post current IP address to .php PatheticalPanic Linux - Networking 3 06-27-2006 12:37 AM
thread switch results in kernel stack switch superstition Linux - General 1 05-17-2005 11:48 PM
set up DSL thru SWITCH - winXp connected to SWITCH too husz Linux - Newbie 5 04-22-2004 12:08 AM


All times are GMT -5. The time now is 12:36 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration