lilo.conf Permissions???????
Man, how do I get permissions to modify this file?
I mean I'm in Super User File manager, root , and it won't let me do it.
I even tried doing this trick: "Knoppix single" booting to the command line then "startx".
Usually that lets me do anything.
Not now. What's the trick to this one? The modified lilo.conf file is in my Home directory right now. All I have to do is move it.
Is there some special chmod code I need for this file?
Anyway, I made a small change in my bios in the power management section. I changed a setting to "video always on." It had been using a suspend setting, which I had not realized. Perhaps that's it. Maybe I should see if that fixed it before I do anything else.
PNP has always been turned off so that was not it.
The weird thing about this problem is that I can boot the computer for dozens of times and everything will be fine. But if the screen goes kablooey for a second or two then comes back.... I know the usb is gone.
I noticed on the boot CD that there is some sort of interactive relationship between usb and apm according to the messages I see on screen. I have not noticed this while booting from my HD installation.
sakiZ
Whole New Set of Problems :-)
Well, first the good news. After tinkering with my module conf file for the 2.6.9 kernel I am able to boot into the 2.6.9 kernel on my Knoppix 3.7 HDD install. Wow. I never thought that would happen. I about fell off my chair.
I wanted to see if my external USB DVD-rw drive could be found. After doing a "lsusb" I discovered Linux does see the USB External DVD-rw drive as an "sda" mass storage device. I was expecting an "scr2" or similar. Hmm.
Although I went ahead and made a mount point for the drive called "DVD-USB-Storage" in fstab, and I can mount and read the drive like this, it's not what I was really looking for as K3b does not see it as a writeable drive. So, it is usable to pull info off the DVDs I have made as backups. But no more than that.
So, for the time being I'll just keep using the 2.4 kernel.
Any thoughts on this?
sakiZ
Hmmm, That's what I was afraid of.
Quote:
That could be just a problem with scsi devices on 2.6.9,
Yeah, I was wondering if that was the case.
Well, I won't be putting much energy into it.
The 2.4 kernel is doing everything I want for now.
sakiZ