Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Help!



Hi

I think you're setting the I/O port in autoexec.bat and that is 
screwing up your setup.

>>>From jmt at nda.com:
[x]

 > --begin /var/log/kernel--
 > Nov  3 20:17:10 belle kernel: ad1848_detect(534)
 > Nov  3 20:17:10 belle kernel: ad1848_detect() - step A
 > Nov  3 20:17:10 belle kernel: ad1848 detect error - step A (ff)
 > --end /var/log/kernel--
 > 
 > --begin ad1848.c--
 >   /*
 >      * Check that the I/O address is in use.
 >      *
 >      * The bit 0x80 of the base I/O port is known to be 0 after the
 >      * chip has performed its power on initialization. Just assume
 >      * this has happened before the OS is starting.

So, it's failing because the 0x80 bit is on [if I'm understanding 
it]. And the bit about "Just assume this has happened before the OS 
is starting" makes me thing that the initialization you're doing in 
autoexec.bat is causing this test to be true [error condition].

 > 
 >   DDB (printk ("ad1848_detect() - step A\n"));
 >   if ((inb (devc->base) & 0x80) != 0x00)	/* Not a AD1848 */
 >     {
 >       DDB (printk ("ad1848 detect error - step A (%02x)\n",
 > 		   inb (devc->base)));
 >       return 0;
 >     }
 > --end ad1848.c--
 
 > --begin AUTOEXEC.BAT--
 
 > VOLSET /V:14 /X:14 /F:14 /C:14 /L:14 /M:14 /R:L
 > HWSET /SBA:220 /SBDMA:1 /MSSA:530 /SBIRQ:5 /GPA:E /MSS:E

I think these two lines [above] are your problem. What if you boot 
into Linux without running any of this stuff? 

 > --end AUTOEXEC.BAT--

 > Help?

Good Luck!

--
John Saylor MIT E40-335 617.253.0172






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org