Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: "iforone" <floydstestemail@xxxxxxxxx>
- Date: 11 Jun 2006 15:52:57 -0700
iforone wrote:
Moe Trin wrote:
OK - let's clarify this - when you reboot to get it to work, it this a
power-cycle (or front panel reset button), or just the three-finger-salute?
It doesn't seem to matter whether or not ctrl+alt+del was used - or
logout/shutdown, from the Debian(KDE) menu, or if it's from a 'cold'
boot - no difference either way :-(
[ Correction ]
Whoops - I thought you were asking about while when switching OSes -
but anyway, to answer your above question(s) - I _think_ I (in win98,
where my problem exists, after using Debian) usually just -->Start Menu
| Restart.
[ /Correction ]
I will now go and try again, and see if the 3finger salute makes a diff
or not - I'll report back
OK I'm back... - and yes it seems the 3 finger salutation does the
trick too...i.e.; the same thing occurs as when using Start | Restart
from within win98 (same as rebooting) -- details at the bottom (after
my "mount" dilemma and resolution)
[ 'mount' dilemma ]
Besides I need to reboot anyway, since I can't seem to 'umount' hda1
properly,
To mount my hda (win98 only + plus and old dilapidated and corrupted
Debian install)
I did;
~$ sudo mkdir /mnt/tmp
~$ sudo mount -t vfat o,uid=username,ro /dev/hda1 /mnt/tmp # this
failed
~$ sudo mount -t vfat -o,uid=username,ro /dev/hda1 /mnt/tmp # this
worked
Like an idiot, I mounted hda1, when I needed to mount the whole hda
(all 3 win98 partitions)....but I *should* be able to just easily
umount it and remount the whole hda - but n-o-o-o :-( woe is me...
....I've tried many (different) iterations of umount and mount;
~$ sudo umount /dev/hda1 /mnt/tmp
umount: /mnt/tmp: device is busy
umount: /mnt/tmp: device is busy
umount: /mnt/tmp: device is busy
umount: /mnt/tmp: device is busy
~$ sudo umount -r ro /dev/hda /mnt/tmp
umount: ro: not found
umount: /dev/hda: not mounted
umount: /dev/hda1 busy - remounted read-only
~$ cat /etc/mtab
/dev/hdc1 / ext3 rw,errors=remount-ro 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
tmpfs /dev tmpfs rw,size=10M,mode=0755 0 0
/dev/hda1 /mnt/tmp vfat ro 0 0 # <--this is the win98 mount table entry
so I tried these;
~$ sudo mount -o ro /dev/hda /mnt/tmp
mount: you must specify the filesystem type
~$ sudo mount -t vfat -o ro /dev/hda /mnt/tmp
mount: /dev/hda already mounted or /mnt/tmp busy
mount: according to mtab, /dev/hda1 is already mounted on /mnt/tmp
Big Note; hda is NOT listed in my /etc/fstab which likely plays a role
in this unmounting ability too - but I can recall this umounting pita
also occuring when there were entries in /etc/fstab for hda - and even
when the entries were made to load, but not mount upon boot;
(something like this)
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/hda1 /mnt/hda1 win95 noauto,nouserid,noexec 0 0
I even tried remounting read-only, which is what I wanted anyway. Using
'mount -r' does indeed remount read-only (see my last 2 mount commands
above in this post). I always get device is busy (no worry, for another
time and place ;-))
Oh - I solved the mount issue it seems...It was stupid KDE - once I
closed it out, right before shutdown/reboot, I successfully umounted
hda1 - no more entry in /etc/mtab. Though I still have a issues with a
bad superblock (or unrecognized filesystem) on that hda.
~$ sudo mount -t vfat -o ro /dev/hda /mnt/tmp
mount: wrong fs type, bad option, bad superblock on /dev/hda,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
....yeah ...yeah I know - but hda has my working win98 system (and a
really munged Debian install leftover, I think)
~$ dmesg | tail
FAT: invalid media value (0xb9)
VFS: Can't find a valid FAT filesystem on dev hda.
FAT: invalid media value (0xb9)
VFS: Can't find a valid FAT filesystem on dev hda.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev hda2.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev hda3.
FAT: invalid media value (0xb9)
VFS: Can't find a valid FAT filesystem on dev hda.
Well -- that's finally done and solved...what a pita :-/
[ /mount dilemma ]
Back on Topic;
Details of win98 IPCONFIG (actually Winipcfg) after closing out Debian
and booting into win98
=====================================
/////////////////////////////////////
Windows 98 IP Configuration
Host Name . . . . . . . . . : FUCKYOUBILLYRAT <--no joke
DNS Servers . . . . . . . . :
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No
Ethernet adapter :
Description . . . . . . . . : NETGEAR FA31X PCI Adapter
Physical Address. . . . . . : 00-00-00-00-00-00 <-- Note No MAC addy
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 169.254.196.62 <--here's the ratbag's
idea
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 06 10 06 5:27:00 PM
Lease Expires . . . . . . . :
==== Below is a Working config - After the 3 finger salutation =======
(or just a Start Menu | Restart)
Windows 98 IP Configuration
Host Name . . . . . . . . . : FUCKYOUBILLYRAT
DNS Servers . . . . . . . . : xxx.206.251.15
xxx.206.251.16
xxx.206.251.79
^^^^^
xxx's used in place of legitmate working 1st octet
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No
Ethernet adapter :
Description . . . . . . . . : NETGEAR FA31X PCI Adapter
Physical Address. . . . . . : 00-0x-xx-xx-xx-xx <--Real MAC addy x-ed
out
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.0.2 <--#PC addy DHCP via Router
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.0.1 <--#Router addy
DHCP Server . . . . . . . . : 192.168.0.1 <--#Router addy
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 06 10 06 5:30:46 PM
Lease Expires . . . . . . . : 06 13 06 5:30:46 PM
/////////////////////////////////////
=====================================
more Drats - how'd my last post get s-o-o-o... darn l-o-n-g :-$ ????
and now this one too :-(
Regards
.
- Follow-Ups:
- References:
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: iforone
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: Moe Trin
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: iforone
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- Prev by Date: Stats comp.os.linux.networking (last 7 days)
- Next by Date: Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- Previous by thread: Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- Next by thread: Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- Index(es):