iB::Topic::Unable to edit "bootlocal.sh"

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Laptops » Unable to edit "bootlocal.sh"

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (2) </ [1] 2 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Unable to edit "bootlocal.sh"

< Next Oldest | Next Newest >

Privateer187 Offline

Group: Members
Posts: 4
Joined: Dec. 2005

Posted: Dec. 18 2005,03:20

Hello. I have an old Toshiba 445 CDX laptop which I recently installed DSL 2.0 on. It works great and the systems is snappy and responsive, but the sound does not work beyond system beeps. I searched the forums and found a fix to try involving adding an addional line to opt/bootlocal.sh, but the system will not let me edited it in Beaver. How do I fix this?

Please bare in mind, I'm only moderately proficient at Linux and not the best in the world with the command line, so please spell out in complicated/non-blatant responses. Thank you all in advance.

Privateer187 Offline

Group: Members
Posts: 4
Joined: Dec. 2005

Posted: Dec. 18 2005,05:48

Okay, the above was a stupid error on my part, and I figured it out. I was used to live cds that automatically grant one root access, and I forgot to change to root to change the file. But I still haven't fixed the issue. I added the line:

#modprobe opl3sa2 io=0x370 mss_io=0x530 mpu_io=0x330 irq=5 dma=1 dma2=

To bootlocal, and I still can't get anything out my speakers besides the system beeps. Any other ideas or resources?

clacker

Group: Members
Posts: 570
Joined: June 2004

Posted: Dec. 18 2005,14:09

you didn't have the # symbol at the start of the line, did you? That would have commented out that line and kept it from executing.

Have you tried running the command from an xshell using the live CD? Did it work then? You might need to do something like sudo modprobe ... or sudo insmod ... to get it to work instead of just modprobe (again without the # symbol).